How we work
From the first call to a system your team actually uses.
Four steps, the same every time. You know the price before anything is built, you see working software at every milestone, and you can stop at any step.
At a glance
- Discovery callFree · 30–45 minutes
- Scoped planFixed price · about a week
- Build & integrateTypically 3–10 weeks
- IterateTuned on real usage
01 Step by step
What happens after you get in touch.
Each step says what you receive, what we need from you, and the decision that is yours to make before the next one starts.
-
01
Discovery call
Week 0 · free · 30–45 min
We map how the work runs today — the systems, the data, the people — and what “solved” would look like for your team.
- You get
- An honest first view: worth doing, not worth doing, or not yet.
- We need from you
- Someone who feels the problem, and ideally an example of the work.
- Your decision
- Continue to a scope — or stop here, at no cost.
-
02
Scoped plan
About a week
We write down exactly what will be built, in what order, the timeline, and a fixed price. Assumptions and exclusions are named.
- You get
- A document you can say yes or no to — and show to whoever signs off.
- We need from you
- Answers to our questions, and a look at sample data or documents.
- Your decision
- Sign the scope — or walk away with the document.
-
03
Build & integrate
Typically 3–10 weeks
We build against your real systems and show you a working system at every milestone — never a single reveal at the end.
- You get
- Software running in your environment, and the engineers who built it.
- We need from you
- Access to the systems involved, and someone to review each milestone.
- Your decision
- Accept each milestone. Scope changes are raised the moment we see them.
-
04
Iterate
Ongoing
Once your team uses it, we watch real usage and tune it to how people actually work — not how we assumed they would.
- You get
- Fixes, tuning and extensions based on evidence, plus support you can reach.
- We need from you
- Feedback from the people using it.
- Your decision
- Extend it, hand it over, or move to the next workflow.
02 What to expect
No surprises along the way.
The same commitments apply whether we are building an automation, deploying SolmiriX or running a readiness engagement.
- Direct communication
- You talk to the person doing the work, not a layer of account management.
- Working software, not slides
- Milestones are shown in a running system you can click through.
- Scope changes, said out loud
- Bigger or smaller than planned? You hear as soon as we know.
- You can stop
- At every step, with what you have received so far.
03 Questions
Questions about the process.
Can we stop after the discovery call or the scope?
Yes. The call is free, and the scope is yours to keep whether or not you go ahead. Nothing is billed open-ended.
What if the scope changes during the build?
You hear about it the moment we see it — not at delivery. Any change to price or timeline is agreed in writing before work on it starts.
Who do we talk to during the project?
The engineers building your system. There is no account-management layer between you and the work.
What happens after launch?
The Iterate step covers tuning against real usage. Ongoing support and extensions are agreed in the scope, so you know what is covered.
Start with a 30–45 minute conversation.
Tell us what you are working with. We will tell you honestly whether — and how — we can help.