Direct answer
ARCHITEKT stands up ventures on a client's account. The mandate can cover proposition, product, technology, operating model, governance, team and launch, with a named operator holding the build until client ownership is ready for handover.
What the mandate can cover
- Proposition and business model
- Product and technology
- Operating model and governance
- Team build and first hires
- Launch
- Handover to client ownership
Venture Building is not Venturing
Venture Building is on the client's account. Venturing is ARCHITEKT's own account: those ventures are evidence of how we build, not client engagements.
What standing a venture up actually involves
Six things, and the mandate can cover any subset. The proposition and the business model behind it. The product and the technology that serves it. The operating model and the governance that will run it. The first hires. The launch. And the handover to client ownership.
The part that decides the outcome is the team, and it is the part most often left until last. A venture handed over to people recruited after the build has to relearn every decision that was made without them; a venture whose permanent team was hired during the build inherits the reasoning as well as the code.
A named operator holds the seat until that team can hold it. The seat is vacated on an agreed date rather than when everyone feels ready, because a venture that still depends on the builder has not been handed over — it has been lent.
The executive accountability stays with the client throughout. ARCHITEKT builds the activity; it does not own it, and it does not take equity in it.
What it is not
It is not a venture studio. A studio builds on its own account and keeps equity; this builds on yours, and ends with the operator seat vacated rather than with ARCHITEKT on the cap table.
It is not Build Direction. Build Direction directs a construction inside an organisation that already exists, with its teams, its vendors and its constraints. Venture Building stands up an activity that does not exist yet. Where there is no organisation around the build, the mandate is a venture — and that single criterion is how the two are told apart before either is signed.
It is not the Werks. Those three ventures are built on ARCHITEKT's own account and are not for sale: they are the evidence behind this offer, not a version of it.
The measure
The venture runs, the client owns it, and the operator seat is empty on the date that was agreed at the start. All three, not two of the three: a venture still dependent on the builder has been lent rather than handed over, and the dependency is easiest to see on the day the seat is meant to be vacated.
Exit
The venture is handed over standing: owned by the client, run by its own team, with the operator seat vacated on an agreed date.
Capabilities mobilised
Where it has run
Questions
- How is this different from your own ventures?
- AnKre, Phoeniks and On-Kare are built on ARCHITEKT's own account. They show how we build. A Venture Building mandate builds on yours, and ends in your ownership.
- Who runs the venture at launch?
- A named operator holds the build until client ownership is ready; the permanent team is part of the mandate, not an afterthought.
- How is this different from a venture studio?
- A studio builds on its own account and keeps equity. This builds on yours: the venture is client-owned from the start, and the mandate ends with the operator seat vacated on an agreed date rather than with ARCHITEKT on the cap table.
- How long before the venture stands alone?
- The build is measured in quarters, not weeks, and handover is a phase rather than an event: the permanent team is recruited during the mandate, not after it, so the operator hands to someone who was already there.
- What is this not?
- It is not Build Direction. Build Direction directs a construction inside an organisation that already exists, with its teams and its constraints. Venture Building stands up an activity that does not exist yet — if there is no organisation around it, it is a venture.