Home/How we work
How We Work
Most of the anxiety in a custom software project comes from not knowing what happens next.
Here's the whole process, in order — including what we need from you, when you'll see something working, and how we handle the fact that our team sits on the other side of the world.
1. Discovery
We start with a call about how your agency or product actually runs. Not a demo, not a sales pitch.
We'll ask about your payer mix, the states you operate in, how visits are scheduled and verified today, where the manual workarounds live, and what a good outcome looks like six months out.
What you get: a written summary of what we heard, and a straight answer on whether custom software is the right call. Sometimes it isn't, and we say so.
2. Scope and estimate
You get a written scope with milestones and a fixed price for phase one.
Not an open-ended hourly block. If the scope changes, we change the document and you approve it before the work moves.
3. Build
Two-week increments. You see something clickable at the end of the first one, not at the end of the project.
If you have a repo, a board, and a process, we work inside them. If you don't, we'll set something up and hand it over.
4. Launch
A cutover plan, training for your office staff and your caregivers, and written documentation.
If you're migrating off an existing system, we run the old and the new in parallel until you're confident enough to switch.
5. After launch
Either an ongoing support agreement, or a documented handoff to your internal team. Your call, agreed in the contract rather than negotiated later.
How remote collaboration works
Our team works on UTC+8. Here's what that looks like in practice:
- Async by default — written specs, walkthrough videos, and a shared chat channel
- Live calls scheduled inside your business hours, not ours
- Documentation written in English as standard, not as an extra
- One named point of contact who answers, so you're not chasing five people
How we charge
Phase one is fixed price, based on the scope we agree together. After that, most clients move to a monthly rate for an ongoing team.
We don't publish hourly rates. The honest answer depends on team size and scope, and we'd rather quote your project properly than post a number that's wrong for it.
What we need from you
- Access to the people who actually know the workflow, not only the person signing the contract
- A decision-maker who can approve scope changes without a committee
- Sample data or read access to your current system during discovery
- Your compliance requirements early, not at the end
Common questions
How long does the first phase take?
A focused first phase usually runs 6–10 weeks from signed scope to something you can use. We give you a written estimate with milestones after discovery, before you commit to anything.
Do we need to be available during your working hours?
No. That's the point of running async. We schedule live calls inside your business hours and handle the rest in writing.
What if we don't have detailed requirements yet?
That's the normal starting point. Discovery exists to turn a rough idea into a scope you can actually approve.
Can we talk to your existing clients?
Our current clients are care operators in China, and a reference call across a language barrier wouldn't tell you much. What we can do instead is show you the systems we built — a live walkthrough of the actual product, with the engineering decisions explained. If you still want a client reference, we'll ask one and arrange it with translation.
What happens if we're not happy mid-project?
You'll have seen working software every two weeks, so there shouldn't be a surprise. If something is going wrong, you'll hear it from us before the deadline rather than after it. Wind-down terms are in the contract.
The first call is about your workflow, not our pitch.
Thirty minutes, and you'll know whether we're worth a second one.