Ikigai “I'm starting something new.”
MVP development — from idea to working product.
You have an idea, and probably a deadline: an investor meeting, a market window, a moment of conviction that won't last forever. What you don't have yet is a version of it small enough to get in front of real people — and the evidence that only arrives once you have.
Ikigai is how we take an idea to a real, usable MVP: scoped honestly, built properly, and released to real people while the question is still cheap to answer.
What it is
Ikigai is the work of deciding what deserves to exist. Before anything is built, the questions worth answering are which problem is real, who actually has it, and what the smallest honest version of a solution looks like.
The output is not a prototype to look at. It is a product people can use, small enough to build quickly and complete enough to tell you something true.
生き甲斐 a reason for being
The four-circle diagram that circulates online — passion, mission, profession, vocation — is a Western invention layered onto the word much later. In Japanese, ikigai is humbler and more ordinary: the reason you get up, as likely to be a small daily thing as a grand purpose.
We use it in the plain sense. Before anything is built, the question is what would make this worth existing at all — for the person using it, not for the person funding it. Most software that fails was never able to answer that.
What you end up with
A working product in real hands, a scope you can defend, and evidence about whether to continue.
How the work goes
-
Understand the idea
What the product is for, who it serves, and what would have to be true for it to work.
-
Reduce the uncertainty
Name the assumptions the whole idea rests on, and find the cheapest way to test the riskiest one.
-
Define the product
Decide the shape and the scope — including, deliberately, what is left out of the first version.
-
Build the MVP
A real product, built properly, small on purpose.
-
Put it in front of people
Release it, watch what happens, and read the result honestly.
The shape of it
What an Ikigai engagement looks like
- Duration
- Typically 4–8 weeks from kickoff to a released MVP.
- Scope
- Fixed, agreed together — including, deliberately, what the first version leaves out.
- Price
- Fixed, and known before we start. It changes only if the scope does.
- Output
- A working product in real hands — not a clickable mock-up — plus source, documentation, and the evidence: what users did and what we'd do next.
- After
- You own everything. Continue into Kaizen, take it to an internal team, or stop with a clean result. All three are fine outcomes.
When the agent is the product
Some MVPs have a conversation where the interface used to be.
An agent your customers talk to, that answers from your data, takes actions on their behalf, and hands off to a human when it should.
Anyone can vibe-code a demo of that in a weekend. The distance between the demo and a product is exactly what Ikigai scopes on purpose: what the agent is allowed to do, how you'll know it's answering well — evals, from day one — what each conversation costs, and what happens when it's wrong. Those questions are cheap to answer at MVP size, and ruinous to discover in production.
Choosing correctly
Is this the right practice?
It fits when
You are early, the idea hasn't met real users yet, and you would rather learn something in six weeks than launch something in a year.
It doesn't when
If software already exists and is struggling, the work is repair, not creation.
What it represents
Creation, and the beginning of a product.
Questions
MVP development, answered.
How much does an MVP cost?
It depends on the scope we agree together — but Ikigai engagements are fixed in scope and short in duration, so you'll know the full cost before we start, and it won't change unless the scope does. Write to us with the idea and we'll give you a concrete number after one call.
How long does it take to build an MVP?
Most Ikigai engagements ship in 4–8 weeks. If an idea genuinely can't be tested in that window, the scope is usually wrong — narrowing it is the first work we do together.
What if the MVP shows the idea doesn't work?
Then Ikigai did its job. Learning that in six weeks instead of eighteen months is the entire point. You keep the product, the code, and the evidence.
Can you build an AI or agent-based MVP?
Yes — an agent your customers interact with directly, connected to your data and systems, with evaluation and guardrails built in from the first version. The discipline is the same: smallest honest version, real users, weeks.
I already vibe-coded a prototype. Is that a head start?
Often, yes — it's evidence about what you want. We treat it as a specification, not a foundation: we keep what it taught you and build the production version properly. If it's further along and struggling, that's a Kintsugi situation, and we'll say so.
Do I need a technical background to work with you?
No. Most Ikigai clients are non-technical founders. We handle the technical decisions and explain them in plain language; you stay in charge of what the product is for.
What do you build with?
Conventional, boring, well-supported technology that any competent team can take over later. Cleverness is a cost paid by whoever comes after — including you.
Start here
Tell us where your product is, and we will tell you what we would do next.
No pitch deck required. A short description of the situation is enough for a useful first conversation.