After Decide
You completed Decide with Lirroy or a similar process.
You have a navigable product, architecture, and prioritized backlog. Product in production is what is missing.
From navigable product to production.
Clean slate: no baggage from previous code.
You finished Decide with a clear direction, or you arrive with a well-defined spec. We ship product in production in a real environment, following the architecture and plan you already have.
Who this is for.
You already decided what to build. You have a navigable product, architecture, or a solid plan, and you need to reach production without improvising.
-
-
Closed spec
You arrive with scope and architecture already agreed internally.
You do not need to revalidate the idea: you need a team that executes with senior judgment.
-
Investment ready
You have budget or commitment to build in the coming months.
You want to start on solid ground, not a fragile MVP that will need a rewrite.
How the 15 days unfold.
Live demos on days 5, 10, and 15. No surprises at the end.
-
Week 1
Kickoff and environment
We align MVP scope, production environment, CI/CD, and definition of done. We bootstrap the repo and technical base per the agreed architecture.
-
Weeks 2–4
Core build
We implement critical MVP flows in production-grade code. Periodic demos to validate direction, copy, and UX before deepening secondary modules.
-
Weeks 5–6
Integrations and robustness
Auth, payments, analytics, observability, and minimum viable security. Performance tuning and staging tests.
-
Week 7
Production launch
Production deploy, credential handoff, and documentation. Evolution plan for what stays outside agreed scope.
What you leave with on day 15.
Product in production
Commercializable software deployed in a real environment.
Solid technical base
Repo, CI/CD, and architecture implemented per plan.
Critical integrations
Auth, payments, or others per agreed scope.
Handoff and roadmap
Documentation and backlog for what comes after go-live.
What this looks like in practice.
A typical example after a successful proof of concept.
Before
You have a navigable product, architecture, and implementation plan, but no software in production that can serve real users yet.
After
Core MVP is live with auth, main flows, and minimum observability. Your team or investors can try the real product, not a demo.
Outcome
You move from a buildable decision to product in production, with a base to iterate or scale without starting over.
Questions about this process.
- Not required. Greenfield fits when you already have clear direction: navigable product, spec, or architecture from another process or your team. If you have not decided what to build yet, start with Decide.
- It depends on scope. A focused MVP usually takes 6 to 8 weeks; we agree the exact timeline in the 30-min diagnostic, with concrete phases and deliverables. We work by outcome, with fixed scope.
- Yes, when the prior architecture is solid. If technical decisions need adjustment, we do it explicitly before writing production code.
- Yes. Handoff includes repo, documentation, and prioritized backlog. We design so any competent team can continue.
- Investment depends on MVP scope. We define it in the diagnostic with a phased proposal. We do not publish a single price because every greenfield starts from a different plan.
Ready to take your plan to production?
Book a 30-min diagnostic. No cost, no commitment. If Greenfield is not for you, we will tell you on the same call.
Or email us at hola@lirroy.com