The chain that turns a client conversation into funding. Each answer sets the next step.
Answer these and the placeholders above become real.
Why this block. The unit is now defined, so we know the space, weight and electricity to look for. Electricity is what stops most projects: plugging into a site that already has spare power avoids a wait for a new grid connection that runs for years.
Why this block. Now we have something real to sell — a finished design and a named place to put it. A funder is not buying our optimism, they are buying somebody else's promise to pay.
Why this block. You only get one first meeting with each funder. Go when the design is finished, a site is named and a customer has signed — not before.
Why this block. Not the critical path, but it will block the money at the last moment if left undone. One or two people own this and must never pull anybody off the month's focus.
Why sequential beats parallel here. We are eight part-time people. Split across four workstreams we move each one a few hours a week and finish none of them. Pointed at one thing, a month is enough to actually close it out. It also happens to be the right order — each block needs the one before it finished.
M1 · PodM2 · SitesM3 · CustomersM4 · FundersFundingBuild | |
W1W3W5W7W9W11W13W15W17W19W21W23W25W27W29W31W33 | |
| Month 1 · Weeks 1 to 4The PodEverybody on the unit. Nothing else gets attention. | |
| weeks 1–1Client + funder requirements, and the 'what it must do' sheet | |
| weeks 1–3The engineering pack: electrical, mechanical, layout, structural | |
| weeks 2–4Design freeze, then procurement strategy and costed parts list | |
| weeks 3–4Service quotes for build, install and monitoring; safety plan | |
| Month 2 · Weeks 5 to 8SitesThe unit is defined, so now we know what to look for. Everybody on sites. | |
| weeks 5–5One-page site requirement sheet, electricity number on it | |
| weeks 5–7Write the Site Strategy Document, then work its contact lists | |
| weeks 6–8Chase written proof of spare electricity | |
| weeks 8–8Sign the non-binding host agreement | |
| Month 3 · Weeks 9 to 12CustomersWe have a real unit and a real place. Now it is worth a customer's time. | |
| weeks 9–9Target customer list and the one-page offer | |
| weeks 9–11Customer pitch pack — the pitch, then the questions | |
| weeks 10–11Draft the letter template so it actually commits | |
| weeks 11–12Hold the meetings, get one letter signed | |
| Month 4 · Weeks 13 to 16FundersWalk in with all six proofs in hand. Not before. | |
| weeks 13–13Funder list by stage, and the numbers pack | |
| weeks 13–14Funding pitch and the objections-and-answers sheet | |
| weeks 14–15Evidence folder, and our homework on structures and risks | |
| weeks 15–16Hold the funder meetings | |
| Background · Weeks 1 to 8Company & adminOne or two people only. Must never pull anybody off the month's focus. | |
| weeks 1–6Tax advice first, then form the US and Netherlands companies, open banking | |
| weeks 4–8Confidentiality agreements, insurance quotes, shareholding | |
| Funding decision the gate — everything below waits for this | Negotiate and sign the funding offer · weeks 17–20 |
| After fundingThe Pod | |
| weeks 21–30Cooling simulation, order long-lead items, build, factory test | |
| weeks 30–34Transport, install, full-power heat test, deliberate-failure test | |
| After fundingSites | |
| weeks 21–28Registered lease, permits, groundwork, connect | |
| After fundingCustomers | |
| weeks 21–24Turn the letter into a signed contract |