Method

The first thirty days of a residency

A residency starts inside the operating rhythm, not beside it. The first of three cycles in a twelve-week residency has one obligation: by day thirty, something is shipped and the constraint has a name. Here is how the month actually runs.

Days one to ten — sit inside it

We join the rooms where the business actually happens: pipeline reviews, deal calls, delivery stand-ups, the P&L. We read the last two quarters of lost deals and listen to how the offer is described — by the founder, by the team, by customers. No workshops, no interviews-as-theatre. The constraint shows itself when you watch work move.

Days ten to twenty — name the constraint, agree the build

One page: the constraint, the engine that removes it, what ships this cycle and what doesn't. It's agreed with the founder and said to the whole team in the same words. From here the crew is in build — offer, motion, roles, rhythm — with your people doing the work beside us, because they are the ones keeping it.

Days twenty to thirty — ship the first piece

The first working piece goes live against real customers: an offer in market, a motion running to a cadence, a practice taking its first briefs. Whatever shipped is written down as it's built — the plays, the decisions, the reasons — so it holds without us. Where it fits, on Kamber.

Day thirty — decide

Continue or stop. Either way the month ends with something running and a named constraint — yours to keep. In one recent residency, twelve weeks took an undefined capability to a working data practice with $6M of qualified pipeline.

Humanloop is a company-building practice in Melbourne, founded by the operator who built Riley — acquired by NCS, a Singtel company. hello@humanloop.co