Established business
You run a business and have a platform idea to sell or scale.
You are not yet sure whether the effort, budget, or risk is justified.
From idea to decision, in 15 days.
We build a navigable product using AI, fast, with real code, architecture, and an implementation plan. User-centered design with high visual impact.
Who this is for.
You have a product or platform idea and still lack something concrete to decide whether it is worth building, taking to market, or leaving aside.
-
-
Early stage
You hold a product hypothesis without a navigable artefact.
You need something tangible to pitch it, align the team, or decide whether to continue.
-
Committee or investors
You have a thesis you still cannot back with facts.
You need more than a slide deck for investors, partners, or a committee.
How the 15 days work.
Live demos on days 5, 10, and 15. No surprises at the end.
-
Days 1–3
Diagnosis
Deep dive on the problem, interviews with key stakeholders, goal alignment, and definition of the minimum viable scope. By the end of week one, what gets built is clear.
-
Days 4–9
Design and build, or improve
If you start from scratch, we design flows and build the navigable product in real code. If you already have something built, we audit what exists and work on it.
-
Days 10–13
Technical architecture
Stack definition, data model, systems diagram, and technical feasibility review. If there are integrations with external applications or AI components, we assess feasibility and cost too.
-
Days 14–15
Roadmap and delivery
Prioritized backlog, priority task list, phase estimates, and final presentation with the buildable version of your idea. You leave with every deliverable and a concrete action plan for the next stage.
What you leave with on day 15.
Navigable product
Real codeA fully navigable, responsive HTML interface built with modern standards. Ready to show, test, and evolve.
UI kit / design system Tailwind + Shadcn
Technical architecture
Solid foundationsFoundations defined: stack, data model, and technical (and AI) feasibility assessment.
Systems diagram Data model
Execution roadmap
Day 16 strategyPrioritized backlog and a concrete action plan so you know exactly what to build next.
Phase plan Effort estimate
You leave with the most buildable version of your idea.
Clickable, solid, and ready for your team to move without losing weeks to definitions.
What this looks like in practice.
An example of the situation a Lirroy proof of concept addresses.
Before
The idea lives in conversations, decks, and spreadsheets. Scope shifts depending on who you talk to. You still lack a concrete version that lets you commit to what comes next.
After
You get a bounded direction, a navigable product for that version, architecture, and an implementation plan. What was cut, reoriented, and what ships first is already encoded in the process.
Outcome
You leave with a concrete recommendation and an executable plan, shaped, scoped, and ready for the next step.
Questions about this process.
- You can see Proof of concept from the inside before signing: stage deliverables are available, including exactly how we work and what comes out of each stage. Products that moved from this format into development and production are also documented. Evidence comes before commitment, not after.
- They are enough because scope is tuned to the time box. We do not promise a finished MVP in 15 days. We promise a navigable product, solid architecture, and a realistic plan. That does fit in 15 days, and we do it routinely. AI tools absorb the mechanical work while the team focuses on decisions.
- Yes. It is high fidelity and navigable: built in real code with product-grade look and feel, clickable flows, and final UI copy. Stakeholders immediately understand what they will see when you build.
- Especially. One outcome of Proof of concept is translating your vision into a technical brief any CTO or team lead can read and execute.
- That is still a valuable outcome. The plan includes an honest recommendation on how to reposition it: what is solid, which hypotheses need retesting, and which buildable version is worth pursuing.
- No. Everything produced is yours, delivered ready for any capable team to continue: code repository, credentials and access, documentation, design system, and architecture. If you invite us into the build, that is optional, not a requirement.
- USD 4,500 fixed for the 15 days, no add-ons or open-ended hours. It is a small fraction of full product build cost and buys a confident starting point.
- If you have not decided the idea might be built and are only exploring; if you already completed Proof of concept, have scope defined, and a team ready to execute; if you cannot be available for the key conversations during the 15 days; or if you need legal or regulatory research, which is a different engagement. We will flag that on the diagnostic call.
Ready to validate before you build?
Book a 30-minute diagnostic call. Free, no commitment.
Or email us at hola@lirroy.com