How we work
How We Work, From First Conversation to Long-Term Support
A clear process with something you can see, use, or keep at every stage. Here's what happens, what you get, and what we'll need from you.
A short form. We reply within one business day, Eastern Time.
At a glance
- First step
- A fixed-fee discovery or review, if the scope is unclear
- Progress
- Working software every 1 to 2 weeks
- First release
- Often about 2 months, for a focused scope
- Ownership
- Yours as each invoice is paid
The stages
What happens, step by step
Five stages, from your first message to long-term support, each ending in something concrete.
- 01
First conversation
Send a short form telling us where you're starting. We reply within one business day, Eastern Time. The first call takes 30 minutes. - 02
Plan: a discovery, a review, or a direct proposal
If the scope is unclear or complex, we start with a fixed-fee discovery for new software, or a technical review of software you already run. If the scope is already clear, we go straight to a development proposal. - 03
Design and build
We design the key screens and build in short cycles. You see working software every one to two weeks and can try it yourself. Every change is code-reviewed and covered by automated tests. - 04
Launch and hand over
We launch into accounts in your name: code repositories, hosting, and app store accounts. Your team gets written documentation and a handover session. A focused first release often goes live within about two months; larger systems, complex mobile apps, and enterprise projects take longer and are usually delivered in phases. - 05
Support and grow
We fix defects in our work free for 30 days after launch. After that, choose monthly maintenance or ongoing development. Either side can end ongoing work with 30 days' notice.
Visibility
How you'll see progress
No guesswork about where your project stands.
Working software every one to two weeks
You see and try what's been built, so you can judge progress yourself.
One day-to-day contact
The person who answers your first message stays your main contact through the project.
Plain English
Plans, costs, and trade-offs explained without jargon, so you can decide with confidence.
Quality
How we protect quality
The same practices on every project, from the first release to the smallest fix.
Code review on every change
Every change is reviewed before it becomes part of your software.
Automated tests
Every change is covered by automated tests, which stay with your code.
Documentation
Written documentation and a handover session at launch, so your team or any developer can take over.
Widely used tools
Mainstream, well-supported technologies such as React, Next.js, TypeScript, Swift, Node.js, Python, and PostgreSQL.
The first step
A paid discovery when the scope is unclear, a direct proposal when it isn't
A discovery (for new software) or a technical review (for software you already run) is a short piece of paid work that ends in a written plan and estimate. It's recommended, not required.
We recommend it when
- You have an idea but haven't settled what the first release must do
- The work touches several systems, teams, or sources of data
- You're taking over software that someone else built
- You need a written estimate before you can approve a budget
You can go straight to a proposal when
- You know what needs to be built and what it connects to
- The work is small and well defined, such as one integration
- You already have a specification or designs that answer most questions
A fixed fee
Agreed before we start, so the first step has no open-ended cost.
A written plan and estimate
What we'd build, how, and roughly what it would cost. Like all our work, it's yours once paid.
An estimate, not a final price
On time and materials, you pay for the time actually spent. If you need a firm number, choose a fixed price or a fixed budget per phase.
Working together
What we'll need from you
Good software is built with you, not just for you. These make the biggest difference.
- A decision-maker who can answer questions and review progress
- Access to the systems and data the software needs to work with
- Feedback on each demo, so the next cycle builds the right thing
- Early warning of deadlines, launches, or changes on your side
Clear terms
Your code, your accounts
The basics are agreed up front.
You own what you pay for
Code, designs, and other work become yours as each invoice is paid.
Your accounts, not ours
Code repositories, hosting, and app store accounts are set up in your name.
30 days of free fixes
We fix defects in our work at no charge for 30 days after launch.
An NDA when you need one
We'll sign one before you share anything confidential.
Our agreement or yours
Agreements are with Allkanjari Inc., the company behind Doraventi Labs: our standard agreement and statement of work, or your company's contract.
No long lock-in
Ongoing work runs month to month. Either side can end it with 30 days' notice.
FAQ
Questions about our process
How often will we see progress?
Every one to two weeks, you see working software and can try it yourself.
Can we change priorities during the project?
Yes. How depends on the pricing: on a fixed budget per phase, you swap priorities within the budget; on a fixed price, changes are quoted in writing for your approval; on time and materials, extra work is billed at the agreed rate.
What do you need from us to start?
A short description of where you're starting and what you need. We take it from there with a 30-minute call.
Can you work with our existing team?
Yes. We can work on your product month to month as ongoing development, and every change goes through code review and automated tests.
What if we want to stop?
Either side can end ongoing work with 30 days' notice. Anything you've paid for is already yours, including the code, designs, and accounts.
Start with a conversation
Tell us where you're starting, and we'll suggest a sensible first step.
We reply within one business day, Eastern Time.