intesol.kr
Free diagnostic
Home / Services / 6-Week MVP
SERVICE 03 This site is the output

Six weeks later
A working product

From an idea to a product people actually use, in six weeks. AI agents, internal tools, customer-facing web and app — the shape changes, the timeline does not. You get a deployed product, not a demo.

AI agents Internal tools Customer web · app
PROGRAM SPEC
Build duration 6 weeks
Time to start Within 1 week of signing
Stack Claude API · FastAPI · React
Outcome A shipped product
Code ownership 100% client
Project cost ₩24M–48M
01 · If this is where you are

The problem is not the idea —
it is the distance to validation

SIGNAL 01
Six months in and still writing specs
You are past what documents can answer. If the only questions left need a user with hands on it, it is time to build.
SIGNAL 02
Agency quotes start in the hundreds of thousands
You are getting finished-product quotes for an unvalidated assumption. The first thing to check is not the feature list — it is whether people actually use it.
SIGNAL 03
Investors want to see a screen
The conversation changes character the moment a slide becomes a link. A product with numbers attached is the deck.
02 · How the 6 weeks run

Not completion —
we build to validate

We pick one core assumption and build only the minimum needed to test it. Everything else gets added once there is real usage data.

PHASE 01
Week 1
Define
→ One core assumption to validate, agreed
→ User scenarios and an explicit out-of-scope list
→ Agree the success metric
PHASE 02
Week 2
Design
→ Screen design and data model locked
→ Define core behaviour and the guardrails
→ Model cost simulation
PHASE 03
Weeks 3–5
Build
→ Core feature build · AI agent layer where needed
→ Front-end and back-end build
→ A working build shared once a week
PHASE 04
Week 6
Deploy · handover
→ Put real users on it, collect first feedback
→ Usage instrumentation set up
→ Repository, infrastructure and domain handover
03 · Deliverables

After the contract ends
What remains

Repository, infrastructure and domain all move to your accounts. Nothing stays tied to Intesol.

✓ A deployed product (domain and infrastructure included)
✓ Full source code and repository access
✓ Behaviour spec and guardrail documentation
✓ Usage metrics dashboard
✓ Roadmap for what comes next
✓ 30 days of technical support after handover
CASE #0 · INTESOL.KR
This site
is the result
The Intesol site and its inquiry pipeline are an MVP we built for ourselves. Which means we have lived where the six-week number comes from.
Idea → MVP launch 6 weeks
Core features Agreed scope delivered
Usage validation Test users verified
Avg. session 22 min
04 · Questions we get

Before you sign
What you get to check

Can you build something without AI in it?
Yes. Six weeks is a question of scope, not of whether there is AI in it. Internal tools and customer-facing web or app run on the same timeline; AI agents are simply the shape we get asked for most.
Six weeks — really?
You cut features. Six weeks is a scoping problem, not a development-speed problem, and in week 1 we put in writing what we are not building before what we are.
What about code quality? Can we scale it later?
We write production code, not prototype code. There are choices made to fit six weeks, so the handover document states which parts are provisional and what to touch first when you scale.
Can our own developers take it over?
We build on that assumption. Repository access, environment documentation and a handover session are all included, and your developers can sit in during the build if you want.
Who pays for AI model usage?
It runs on your own API account, so you are billed for exactly what you use. In week 2 we simulate expected usage and monthly cost, and put a hard ceiling in the code.
No sales call
Come at the idea stage
and talk then.
What you can validate in six weeks and what has to wait — we cut the scope with you. This happens before any contract.