Case study · Custom AI Systems
Structuring a product before a line was built
Medfins International came looking for someone to start building. Stallwart started somewhere else: with the questions that had to be answered before anything was built.
- 01The hard questions first
- 02Structure the product
- 03A plan the team could build
- Client
- Medfins International
- Problem
- A product ready to be built, before the questions underneath it had been settled.
- Approach
- Ask the hard questions first and structure the product before any code.
The problem
Arunkumar came to Stallwart expecting the usual: a team ready to start building Medfins International's product. He had sat through plenty of calls with people hired to sound smart, and had learned to expect a pitch and a deck.
The problem was not a shortage of people willing to build. It was that the questions underneath the product, the ones easy to avoid, had not been asked out loud yet.
What was assumed
We need someone to start building.
What Stallwart asked
What has to be true before any of this is built?
What Stallwart built
Stallwart did not start by building. On the calls, Stallwart asked questions, the real ones Arunkumar had been quietly avoiding, and then stayed with them while he worked through the answers. No pitch, no deck. What came out was the shape of the product: the decisions that had to be settled before any code, structured into a plan the team could build from.
- 01
Ask the hard questions first
Not the comfortable ones. The questions Arunkumar had been avoiding came first, because the product could not be structured around answers nobody had faced.
- 02
Sit with the answers
No pitch, no next deck. Stallwart stayed on the call while the answers got worked through, so the decisions were his, settled, not sold to him.
- 03
Structure the product
The settled decisions became the shape of the product: scope and structure clear enough that the team knew what to build and in what order.
The approach
Structure before a line was built.
- 01
The hard questions first
The ones the team had been avoiding.
- 02
Structure the product
Decisions settled before any code.
- 03
A plan the team could build
Scope and shape, clear.
No pitch, no deck. The questions that had been quietly avoided, worked through until the shape of the product was clear.
Engineering decisions
Questions before building
A product built before its hard questions are answered is built on guesses.
The trade-off
Slower to the first line of code, in exchange for a product that does not need rebuilding.
No pitch, no deck
The goal was clarity for Medfins, not a sale for Stallwart.
The trade-off
Nothing to hand over at the end of the call except a decision Arunkumar could act on.
Structure, not features
The engagement was about the shape of the product, settled before code, not features rushed out.
The trade-off
No visible build yet, but a plan solid enough to build against.
In practice
Arunkumar
Founder, Medfins International LLP
Arunkumar said he had paid many people to sound smart on calls with him, while Stallwart simply asked questions: the real ones he had been quietly avoiding, and then stayed with him while he worked through them. There was no pitch and no next deck, and he got off the call knowing what to do.
This work connects to
- Custom AI Systems
- Product architecture
- Regulated industries
Frequently asked
What is healthcare product architecture?
It is the work of structuring a product, the decisions, scope, and shape, before any code is written. For Medfins International it meant answering the hard questions underneath the product first, so the build had something solid to stand on.
Why structure a product before building it?
Because a product built before its hard questions are answered is built on guesses. Settling the decisions first means the team knows what to build and why, rather than discovering gaps mid-build.
Did Stallwart build the product on this engagement?
This engagement was about structuring the product before building. The work was the questions and the decisions underneath them, turned into a plan the team could build from, not features shipped.
What did Medfins International get out of it?
Clarity. Arunkumar left the calls knowing what to do: the hard questions answered, the decisions settled, and the shape of the product clear before any code.
Not sure what has to be true before you build?
We ask the questions you've been avoiding, and leave you knowing what to do.
Last updated: October 7, 2026