Discovery
- Research
- Market signal
SERVICE
Lean startup
Lean means different things to different people, and most people get it wrong. This is what lean actually looks like when it's practiced by a team that's built many products — not a slogan, a discipline.
- Only what's necessary, nothing you just "like to build"
- Timelines matched to your actual validation stage
- Scope calibrated to your context, not a fixed formula
When lean is the right approach — and when it isn't
Lean fits a specific situation: testing an idea before you know the market exists.
Lean startup is the right approach when:
You might need more than lean when:
What lean gets you that a full build doesn't
Lean isn't a fixed scope — it's calibrated to where you are
The right amount of lean depends on how much you've already proven.
Context determines scope. The right amount of "lean" for a two-person team testing a hunch is not the same as the right amount for a team building on top of demand they've already proven.
LEAN SCOPE
Testing an unvalidated idea
Cut to the one thing you need to learn
Early signal, not yet proven
Still cutting more than you're adding
Clear demand, known market
Scope earns its place by evidence
Proven and scaling
Lean gives way to building for scale
More scope justified
Liking to build is the opposite of lean. Lean means only building what's necessary — for where you actually are.
How we get to lean
Experience is the only real teacher here — this is the process that comes from having done it many times.
Validate early
Test assumptions before committing to a full build.
Build with purpose
Turn the strongest ideas into something users can try.
Right-sized timelines
1–3 months to test. 3–6 months for a known market.
Learn through building
Use real usage to decide what comes next.
Work we're proud of
Finance
Bflow
BFlow represents a transformative journey in the automation of the accounting process. Our partnership with this Swedish digital accounting agency evolved from initial technical support to a comprehensive system overhaul, culminating in our role as the main technology partner and investor. This project showcases our ability to modernize legacy systems, scale applications, and support businesses through various growth stages - from startup to market expansion.
- React
Questions we help clients answer
What does "lean" actually mean?
Everyone says they like to build — but liking to build is the opposite of lean. Lean means only building what's necessary to answer the question in front of you, nothing more.
Why do lean projects go over budget?
The problem is rarely budget itself. It's scope creep during the build — small additions that each feel reasonable, until the project isn't lean anymore.
How long does a lean startup build actually take?
One to three months for testing an unvalidated idea, three to six months for a product with a known market. The timeline follows the validation stage.
How do you actually get good at building lean?
Build three lean startups and the third one will be the leanest. Experience is the only real teacher here — there's no shortcut around having done it before.
What's the best way to brief you on what "lean" means for us?
Show us specific examples of lean products you admire. "Something like Amazon but minimal" isn't a useful brief — a concrete reference tells us far more than a comparison to something enormous.
Recommended reading
Picked for founders about to test an idea for the first time
Development
How to choose an MVP development company (and avoid the expensive mistakes)
Choosing an MVP development company determines whether your first version teaches you anything useful. Pick well, and you get a product that tests your actual hypothesis with real users. Pick badly, and you get code you cannot extend, data you cannot trust, and a few months you cannot get back. I have run Milo Solutions for sixteen years and watched founders make the same avoidable mistakes here. This guide covers how to evaluate partners and where the real risk sits.
14 min read
Read more
Development
MVP development cost: how much does it really cost to build an MVP?
Every founder who asks me what an MVP costs has read three articles saying the answer sits between $10,000 and $500,000. That range is true and useless for building a budget.Most MVPs land between $45,000 and $91,000, the standard row in the cost table below: 700 to 1,200 hours at senior Central and Eastern European rates. A thin slice starts at $19,000 and marketplace work reaches $190,000. Where you fall comes down to five things: how much you build, who builds it, what you connect to, how much design you buy, and what you commit to after launch. The number follows the scope.
14 min read
Read more
Development
MVP testing: how to validate your product before a full launch
The expensive way to find out that nobody wants your product is to build it all and launch. The projects that reach me in the worst shape are the ones where a founder spent nine months on engineering questions before answering the demand question, and then watched the signups flatten within weeks.MVP testing means checking that people want and will pay for your product before you build it. Name the assumption that sinks the idea if it turns out to be wrong, pick the cheapest test that measures what people actually do, set your pass threshold in advance, then decide whether to build, pivot, or stop.CB Insights examined 431 venture-backed companies that shut down since 2023 and identified the reason for failure in 385 of them. Of those 385, 43% had poor product-market fit and 70% ran out of capital, which the report treats as the final cause of death rather than the root problem; and because the analysis assigns several reasons to each company, the percentages total more than 100. Companies rarely run out of money doing something customers were desperate to pay for.
14 min read
Read moreReady to build only what you actually need?
Let's figure out exactly what "lean" means for your product, and how long it should actually take.
- Free consultation
- Tailored approach
- No obligation
