The delivery logbook / Vol. 01

How not
to deliver a
cooking robot.

35 robots. One garage.
A very stubborn oil pipe.

Rohin

Co-founder, Posha

4 July 2026

FIG. 01 — One robot, one rental, zero room for groceries.

DAY 0

Let’s start deploying.

I land in San Francisco.

I driver over to the site of our office-cum-garage, to see this beautiful sight of our bots waiting and am raring to go. Let’s start shipping!

FIG. 02 — Thirty-five robots waiting politely for the plot twist.

We’ve been in R&D for a while and then setting up a production line for these bots has been a challenge as well. But we’re now past that stage and finally closer to being in real homes.


I open up a bot to run some checks. Oil not flowing. Ouch.

Open another bot. Oil not flowing.

Open another. Oil not flowing.


Why? Let’s talk to the team. These were all tested and verified before being shipped!

After a complete day of grueling debugging with the team we figure out what’s the reason.

We discover all the robots have a pinch in the pipe! A pinch means the pipe was getting constricted and this was preventing the oil to flow.

FIG. 03 — The image of the “pinch”. This image will haunt me for a long time.

But how did this happen? We’ve spent weeks on ensuring exactly issues like these don’t happen.

We realize the pipe length cut was 3 mm short of the intended length and as a result it was overstretched during assembly resulting in the pinch.

I go to sleep trusting the team will come with a solution.

Day 1

I wake up, go for a run.

The Hardware Team tells me a solution to fix the oil-not-flowing problem.

I will now have to unpack all 35 robots, make the fix for oil-not-flowing problem, run some tests and pack them all again.

Day 2-5

I follow a tight schedule.

The daily routine:
Wake up → Run → Unpack bot → Repair → Pack → Do other founder work (which is a lot!) → Sleep.

I get 20 robots ready in 4 days.

Day 6

The first two deliveries.

A big day. Our first two in-person deliveries to two users — let’s call them User A & B.

I come back from the deliveries. I go back to sleep to catch up on my jet lag. I wake up. I see a litany of error messages on Slack emanating from the robots I’d just deployed a couple of hours back.

Turns out that User A’s bot has an issue with the induction system.

And there are many problems occurring with dispensing seasonings.

Not a problem, we can roll out some software fixes — can’t we? No — we can’t. The relevant team is on leave. All of them. All at once 😓

Day 7

I go back to User A’s place. While the main Induction System issue is resolved — I discover something else. The oil is still not flowing 😰🫢😮🙀

And it hits me. So so hard. Because I realize something —

The solution told to me by the team for the oil-not-flowing problem is not working.

And that I’ve already readied 20 bots with a fix that’s not working.

And it’ll have to be redone again.

I let it sink in. I stare at a big mountain of work.

Day 8

The Hardware team tells me a new solution to the oil-not-flowing problem which will now take much more longer to implement but hopefully will resolve the problem for good.

Day 9

I test it out and it works. But there is a catch. Who will do this all over again?

Day 10

A quick mental calculation.

I sit back and think, should we fly someone in from India? I do a quick mental calculation.

The time to get 35 robots ready

Time to

Me

Fly someone in

Plan travel + book + fly

-

4–5 days

Acclimatize / jet lag

-

2–3 days

Repair 35 bots

5 days

5 days

Total

5 days

13–14 days

I take a chance on myself, can’t afford to lose so many days when we’re already running late.

Always → speed above all else.

Day 11–15

I follow a set schedule:

Back to the workbench: Wake up → Morning run → Unpack bot → Repair oil pipe → Pack bot back → Manage org / work with team / IST check-ins → Sleep → Repeat next day.

In 5 days we have 35 bots ready.

FIG. 04 — The garage discovers its manufacturing era.

FIG. 05 — Same garage, somehow fewer places to put a coffee.

I’ve also collected all pieces of oil pipes that were cut and replaced. Like battle scars that you want to remember so that you don't make the same mistake again.

KEEP THIS.
REMEMBER WHY

FIG. 06 — The offending pipe collection.

Day 16

Finally the big day! All bots are ready and we’re all good to go.

But there is another twist in the tale. Something else is about to happen.

Our car breaks down — and guess what’s the problem with the car!

The car’s engine oil is leaking 😞😂

FIG. 07 — The car joins the oil-problem solidarity movement.

Day 17

But we can’t be stopped, can we!

So what do we do?

We rent a new car!

Day 18

On the road. Finally.

A new dawn. I see a fiery red sun rise from my window. Will this be the day?

FIG. 08 — The sun clocks in before the delivery driver.

There’s a lot left to build.

We’re building robots that become part of everyday life. If that’s the kind of work you want to do, we’d love to meet you.