What “first working link in week two” actually means

What “first working link in week two” actually means is the claim buyers should pressure-test before they email a SaaS partner. It is not a finished product on day fourteen. It is a real URL, early enough to argue with, on hosting shaped like production, with the core workflow stubbed so you can click through and say what feels wrong.

What is on that link

Usually: a path through the main job the product exists to do. Sign-up or login may be rough. One happy path works end to end. Data persists. It runs on accounts you can see, not a designer’s laptop. Screens will look unfinished. Roles beyond the primary user may be missing. Integrations, polish, admin tools, and edge cases wait. Billing may be a placeholder. Emails may be stubs. None of that means the link is fake. It means the link is early on purpose.

I’ve watched founders open week-two links expecting a pitch deck’s entire wishlist. That is the wrong test. The right test is: can I do the one thing that matters, and can I tell the team what to change next? If the answer is yes, week two did its job even if the buttons still look ugly.

Why week two exists

The early link exists so feedback starts while change is cheap. Big-bang reveals after two silent months are how you discover the wrong workflow when the invoice is already large. Week two is a conversation tool. You use it. You tell us what feels wrong. We change it. That loop is the point of Eight Mile’s SaaS delivery shape: build where you can watch, first working link usually week two, idea to live typically six weeks for a focused first release. Fixed price after survey. Code and cloud in your name from the start.

Week two vs the six-week first release

Week two is a stub you can steer. The ~six-week first release is a scoped MVP you can put in front of real users with a straighter face: the core workflow solid enough to launch, still ruthless about what waited. We wrote the wider arc in Build a SaaS in 6 weeks. This piece only demystifies the week-two milestone so the two dates do not blur into “full SaaS in a fortnight,” which nobody honest can sell. Soft path when the work is a slice of a larger eng team: software development.

What you must bring for the claim to hold

Ruthless scope. One primary user, one core workflow, must-haves named before week one. Wishlist projects break week two because there is no “one thing” to stub. If you need six personas and four integrations on day fourteen, you do not want this delivery shape. You want a longer discovery and an honest calendar, not a compressed miracle.

Failure modes cut both ways: agencies that vanish until month two, and buyers who treat the week-two URL as done and stop giving sharp feedback. Both waste the only advantage of going this fast.

Is this the delivery shape you want?

If what “first working link in week two” actually means matches how you buy software (early URL, hard scope, fixed price after survey, accounts you own), the next step is a conversation, not another timeline myth dressed up as a roadmap.

Week two to steer. Week six to launch a focused first release. Not a finished empire on day fourteen, and not a silent build until month two either.

If that is the shape you want, contact Eight Mile and say the one workflow the week-two link must prove.