The First Four Weeks: Research Week, Then Three Build Weeks

Requesting a Monday is free and needs no card. You pick an open week from a live grid showing real remaining capacity, and Mindlyft emails you a link. Opening that link holds your chosen Monday for about a week while you book the 30-minute call where the scope and a flat fee for the work get agreed. If the email is never opened, the request simply lapses on its own and holds nothing, there is no silent charge or default booking. Nothing is actually booked until you say yes on that call.

Mindlyft maps your stack, your CRM, and specifically the calls and conversations where commitments currently get dropped before they land anywhere a team can act on them. That mapping is not a generic audit; it is scoped to the systems and tools you actually run, because the build plan that comes out of it has to be buildable inside those exact accounts. The week ends with a written build plan you can read in a few minutes, naming what gets built first and why, which is what the three build weeks that follow actually ship.

The plan written in the research week, built inside your own accounts, with one request in motion at a time and work shipped on a weekly cadence rather than held until everything is finished at once. Iteration happens during these weeks too: a build is refined until it actually holds up against the real stack, not shipped once and left. Nothing customer-facing or that changes a system of record skips a human check during this stretch; the same approval-gated execution that runs the ongoing subscription also runs the first build weeks.

No, only the first one. The research week exists to produce the written build plan an engagement runs on, and that plan does not need to be rebuilt from scratch every cycle once it exists. After the first four weeks, later cycles run on the ongoing subscription mechanics instead: an unlimited queue of requests with one active at a time, shipped weekly, covered on its own page. The research-then-build shape described here is specifically how a new engagement opens, not a pattern that repeats every month.

Whether the work carries on past that point is agreed with you on a call, the same way the original scope and fee were. Nothing renews automatically, and nothing about the first four weeks locks you into a longer commitment by default. If you decide to continue, the engagement moves onto the ongoing subscription queue described elsewhere; if you decide not to, what was already built keeps running inside your own accounts, since none of it depends on a Mindlyft-hosted platform staying online.

You can still request a Monday and say so in the note when you do. For a company that has not made its first revenue yet, billing starts only after that first revenue arrives, agreed in writing on the call rather than assumed either way. This is a deliberate exception for pre-revenue teams, not a workaround: it exists because the research-week-then-build shape is meant to be available to a team before it has the cash flow to pay for it immediately, as long as the arrangement is written down on the call rather than left ambiguous.

Nothing is charged, and no price appears anywhere on the request flow itself: no card, invoice, or bank detail is asked for when you pick a Monday. The flat fee for the work is set on the 30-minute call, once the scope is agreed, as one number for the engagement rather than an hourly rate or a published rate card. That is a deliberate choice, since the actual cost depends on the specific build plan that comes out of the research week, which is different for every team.

Mindlyft takes at most two teams active, in research or in build, in any single week, so that each build gets an engineer's full attention rather than being split across several engagements at once. The week grid shown when you request a Monday reflects real remaining capacity rather than an unlimited calendar, and it updates as other teams request weeks. That is the same reason the ongoing subscription runs one active request at a time per team even after the first four weeks: focus on one build at a time is the constraint the whole model is built around, not an incidental limit.