06_international_expansion/expansion_planning_v0
International expansion plan v0 (working draft)
Target: plan ready and accepted by 4Rooks leadership by 2026-08-05. Status: v0 — initial scaffolding. Will fill in as DACH GTM produces signal.
Why expansion needs a plan, not improvisation
Three reasons:
- Investor signal — a credible expansion plan is one of the things prospective investors will ask for. Having it ready is part of the "attracting investment" target.
- Lighthouse selection has international implications — picking lighthouse customers in geographies we want to expand into amplifies the asset value of those references.
- Capacity constraint — at 4 days/month, expansion cannot be additive on top of DACH execution. It has to be planned, sequenced, and partner-led.
Geo prioritisation principles
| Factor | Why it matters |
|---|---|
| Standards-rich market | KNX, OPC UA, LoRaWAN ecosystems → buyer language already exists |
| German engineering credibility carries weight | Markus's profile + German engineering reputation = warm reception |
| CRA exposure | EU markets share the regulatory tailwind |
| Connected-product manufacturing density | Mid-market OEMs are the buyers |
| Language / sales-cycle compatibility | English + German functional; French/Italian may need a partner |
Tier-1 candidate geos (to validate)
| Geo | Why | Entry model (proposed) | Risks |
|---|---|---|---|
| Switzerland | Industrial / building automation density, German-language, premium spend | Direct, founder-led | Small market alone; usually included with DE |
| Austria | Same as CH; KNX heritage | Direct, founder-led | Small standalone |
| Netherlands | Strong industrial tech, English-fluent buyers, CRA-driven | Direct + 1 partner | Mature competitive vendors present |
| Belgium / Luxembourg | KNX heritage, building automation | Partner-led | Smaller market |
| Nordics (SE/DK/FI/NO) | Industrial automation, agritech (LoRaWAN), strong English | Partner-led, 1-2 referral partners | Distance + need local presence |
| Northern Italy | Industrial machinery cluster (Lombardy, Emilia-Romagna) | Partner-led | Language barrier; long sales cycle |
| France | Building automation, AgriTech, industrial — large market | Partner-led only at first | Buy-French preference; competitive vendors |
Tier-2 (later phase)
- UK — post-Brexit regulatory divergence is a complication; warm market once UK CRA-equivalent stabilises
- Spain — building automation + agritech potential
- Poland / Czech Republic — manufacturing growth, but lower mid-market spend
Out of scope (explicitly)
- US / North America — different stack culture, large domestic competitors, no CRA-equivalent driver. Revisit only if a customer pulls.
- Asia — too distant for a 4 days/month engagement model.
Entry models — three to consider
| Model | When it works | Cost / time | First milestone |
|---|---|---|---|
| Direct founder-led | Where Markus can be in front of buyers directly | Low cash, high founder-time | First customer call within 30 days |
| Referral partner-led | Where ODMs / design houses / distributors already serve our ICP | Low cash, partner enablement | Signed co-sell partner with active intro pipeline |
| Local representative | Once 3+ pilots in a geo justify presence | High cash, high commitment | Hired or contracted rep |
For the first 6-9 months, default: direct in DE/AT/CH, referral-partner-led elsewhere.
Open questions to answer before the plan goes from v0 → v1
- What's Markus's personal capacity for international travel and remote demo cadence?
- Are there existing partner relationships (ODMs, integrators, KNX members) we can lean on?
- What's the cash runway for hiring vs partnering decisions?
- What does the cap-table goal look like for the next funding round, and which geos make that story strongest?
- Are there language constraints on the team (sales conversations, customer support)?
Drafting timeline
- End of month 1 (June 5): v0 → v0.5 — answers to the five questions above gathered
- End of month 2 (July 5): v0.5 → v1 — geo recommendations + entry model + budget
- End of month 3 (August 5): v1 reviewed and accepted by 4Rooks leadership
Last modified 2026-05-05. Suggest a change to this page →