Twelve weeks is not arbitrary
The most common question after the first three is about the build window. Twelve weeks. Why exactly twelve?
The answer is that twelve is the only number that matches the three constraints the model has to satisfy at once.
Constraint one: short enough that the senior leader's attention does not fragment. A senior leader's bandwidth for a side-venture is approximately thirty minutes of synchronous time per week, plus four to six hours of async review per month. That budget can be sustained for a defined window. Beyond about fourteen weeks the budget breaks — the leader's day-job demands reassert themselves, the side-project becomes a guilt object, and the engagement decays into a series of polite postponements. Twelve weeks fits inside the attention window with one week of buffer. Sixteen does not.
Constraint two: long enough that the build is not a demo. A real product — not a wireframed prototype — requires roughly nine weeks of engineering on the Talpro stack. That includes shipping the data model, the auth layer, the core flows, the integrations, the admin surface, the analytics, the accessibility audit, the security headers, the privacy review, and the production deploy. We have done this nine-week core nine times across the eighteen Talpro ventures. We know how long it takes. Anything below eight weeks ships a demo, not a product. The market knows the difference.
Constraint three: long enough that the brand campaign matures. The named-ideator engagement includes twelve months of brand amplification, but the first ninety days of brand work — the announcement, the first podcast, the LinkedIn editorial cadence, the first conference proposal — has to be assembled in parallel with the build. That requires roughly twelve weeks. Less than that and the brand campaign launches before the product is real. The asymmetry is corrosive: senior leader is being credited for a product that does not exist yet, and the moment the product underperforms the launch noise, the credit becomes a liability.
Twelve weeks is the only number that satisfies all three. Twelve weeks of build is also twelve weeks of brand campaign assembly is also twelve weeks of senior-leader attention budget. The arithmetic is a coincidence in the same sense that any well-designed architecture is a coincidence — the constraints converge on a single answer when you write them down honestly.
Inside the twelve weeks the cadence is fixed.
Weeks 1–2. Discovery deepens, blueprint locks, contract package signs. The senior leader reviews the constitution document for the venture. The crew is named.
Weeks 3–6. Core build — data model, auth, flows. One thirty-minute sync per week with the senior leader, focused on the two or three product calls only the leader can make.
Weeks 7–9. Polish, integrations, admin surface, analytics. Brand campaign assembly begins in parallel — first podcast booking is recorded, first IIM lecture is scheduled, LinkedIn editorial drafts are reviewed.
Weeks 10–11. UAT, security audit, accessibility review, payment gateway integration, pre-launch go/no-go. Press kit is finalised, embargoed announcement is drafted.
Week 12. Launch. Demo Day for the cohort. Public press push. First royalty quarter begins on day 1 of revenue.
Weeks 13–52. Brand amplification continues — conference keynote, second podcast, IIM lecture delivered, awards entries. The senior leader's twelve-month brand campaign runs against the now-shipped product.
The cadence is not novel. It is the cadence the eighteen earlier ventures arrived at by trial and error. We are not inventing a build process for cohort 01 — we are running the process the previous eighteen ventures stress-tested.
Why am I writing this?
Because the most common pre-application objection is "twelve weeks sounds too aggressive." It is not. It is actually conservative — relative to what a single CTO with a senior crew and an inheritance of eighteen prior ventures can ship — but the appearance of aggression is real for a senior leader whose mental model of "building software" was set by the four-year SaaS era that AI just compressed.
The four-year SaaS company is what you build when you are bootstrapping a category. The twelve-week brand-attached venture is what you build when you are entering an existing category with a senior leader's pattern recognition as the differentiator. Different problem. Different timeline. Different math.
Twelve weeks is the timeline for the second problem. That is what Maitro builds.
— Bhaskar Anand LinkedIn