The twelve-week product build (and why we won't quote thirty)

Most agencies will quote you a year because most agencies are paid by the month. We are not. We quote twelve weeks because that is the longest a brief should be allowed to drift before contact with reality forces it to either grow up or be cut.

The shape of a Morlabs build looks like this. Discovery for two weeks, where we replace whatever was on a Notion page with a written brief that says exactly what we are building, for whom, and what we are explicitly not building. Design for three weeks, in lockstep with the engineering constraints that will inherit it. Build for six weeks in two-week sprints, deployed continuously to a real URL. One week for launch, one week for hand-off and documentation. Twelve.

The reason this works is that we never start without the brief. The brief absorbs the arguments that would otherwise happen in week eight. The brief turns "should we use OAuth" into a paragraph someone signed off on, not a Slack thread.

If your project genuinely needs longer than twelve weeks, multi-tenant platforms, hardware UIs with safety paths, ML systems that need eval harnesses, we will tell you in discovery. We turn down work that should be smaller and we turn down work that should be bigger. The right shape of work is decided before anyone signs anything.