How we work
How we work: process, security, IP and handover
How most projects run: a free written plan, a price agreed up front, and a handover where you own everything.
Process
Four steps, and you can stop after any of them
Each step stands on its own. You decide after each one.
Get a free plan
Free
Describe the work in a few sentences. Usually within 2 business days a short plan comes back: what to do first, how long it takes and a price range.
A scoping call, if you want one
Free, 30 minutes
We agree how success is measured, the price, a realistic delivery window and what is included.
The build
Usually agreed up front
We start with the smallest version that works and ship it in weeks. The price holds, even if the work takes longer than we estimated.
Run it, or take it
Optional monthly
A monthly care plan with a cap covers monitoring and fixes. Or you run it yourself. You own it either way.
A written note every week. What shipped, what is blocked and what comes next, in plain language, from the person doing the work. Hourly work reports its hours as they are used.
Hiring remote staff instead? That runs as a brief, 2 to 3 profiles, a live task and a paid trial. See how we screen
From the founder
How a project gets scoped, in Faizan’s words
Lines from recorded working calls in 2026. The playbook has the rest: the questions, the red flags and a sample plan.
“The demo has its own timeline and an agreed scope. If the success criteria are met, the contract starts automatically.”
Faizan Naghman, founderOn success criteria, February 2026 “Every work item has hours against it, so the total is a range, and we recommend planning on the midpoint. Running costs like hosting and the database are listed separately from development.”
Faizan Naghman, founderOn estimates, February 2026 “When our reason code matches theirs on the same test set, that's the main game. I build a version, you give feedback, and the loop continues until we reach that level.”
Faizan Naghman, founderOn defining done, March 2026
The Scoping Call Playbook
The 10 questions Faizan asks before anything is built, the red flags and a sample one-page plan. A free PDF, by email.
Get the scoping playbookSecurity
Access you grant, on terms you have signed
We ask only for the access the work needs, in your accounts, under an NDA if you want one.
The plan needs no access
The free plan is written from what you send. A sample file is enough.
NDAs as routine
Yours or ours. Discovery work, partner programs and every paid trial of a remote hire have run under one.
Your accounts, your keys
The build runs in your hosting, databases and mailboxes, in your name. Access comes from you, for the systems the work needs.
One contract, with a US company
Qelv LLC, registered in Wyoming, holds the contract, and ownership of the work is written into the statement of work.
IP and ownership
You own everything, from the first commit
Everything we build runs in your accounts, so your team can keep it running.
- The repository. The code lands in yours from the first commit, under your name.
- The accounts. Hosting, databases, mailboxes and third-party services run in your name.
- The documentation. Written for whoever inherits the system, and handed over with it.
- The handover. A walkthrough at the end of every build, so your team can run the system.
Handover
What arrives at the end of a build
The handover is usually included in the agreed price.
- A working system in your accounts and repository
- Handover documentation
- A walkthrough for the people who will run it
- A report against the measure agreed at scoping
We run it
A monthly care plan for monitoring, fixes and a set amount of change. It has a cap, and you can cancel it.
You take it
Your team runs it from the documentation and the walkthrough. It's yours either way.
Next step
See it on work like yours
A technical walkthrough goes from scope to handover on a system like the one you need. Or start with the free plan.