Plan. Build. Hand over.
How a techcraftz project runs: discover, plan, build in increments, ship and hand over. What you receive at each stage, and what we need from you.
Every project moves through the same four stages. Each ends with something concrete, so you always know where the project stands and what you hold.
| Stage | You receive | We need from you |
|---|---|---|
| Discover | Questions in writing, a view on risks | The brief and access to people who know the problem |
| Plan | A written scope, milestones and a USD estimate | Review, cuts and a decision |
| Build | Working demos at the end of each increment | Feedback within the time agreed |
| Ship | A live product and a full handover | Accounts, approvals and sign-off |
1. Discover
You send the brief. It can be rough: a paragraph, a spreadsheet, a screen recording of the process you want to replace. We reply with written questions. A call is optional, scheduled inside shared hours.
Discovery ends with an honest view. Sometimes that is “build this”. Sometimes it is “you do not need custom software yet” and a cheaper route. We would rather tell you now than after a build.
Output: written questions answered, risks named, and a decision about whether to move to a scope.
2. Plan
We write the scope: what is in, what is out, which integrations are required, which platforms, and how success is judged. It is divided into milestones. Each milestone has a deliverable you can inspect. The estimate is in USD.
You review, cut, reorder or ask for a different split. Nothing is billed for the build until you accept the scope.
Output: a written scope, milestones and a USD estimate. If a prototype is needed to settle the flow, it comes here.
3. Build
We work in short increments. Each increment ends with a recorded demo of working software, and where possible a build you can try yourself on a staging site. Updates are written. A shared task board shows what is done, in progress and waiting.
Changes are normal. When a request falls outside the scope, we re-estimate it in writing and you choose: swap it for something in the scope, add it, or leave it for the backlog.
Output: working software at each milestone, on staging, with a demo.
4. Ship
We deploy to your accounts, with monitoring and a way back if something goes wrong. Then we hand over:
- The repository, in your account.
- Hosting, domains and service accounts, in your name.
- Deployment instructions another developer can follow.
- Documentation of what was built and how it is configured.
- A backlog of what was left for later.
NDA on request, from the first message. You own the code and IP.
Output: a live product and everything needed to run it without us.
After launch
Fixes and updates can continue after go-live. Larger features are scoped as a separate phase with their own milestones. If you prefer to bring it in-house, the handover is built for that.
How we communicate
- Async by default. Written updates on a rhythm agreed at the start.
- Recorded demos. Watch them when it suits you.
- Optional calls. Scheduled in the hours both sides share. Our team works in GMT+7.
- Your tools or ours. We can work in your task board and chat, or share ours.
Engagements that are not projects
Not every need has an end date. For continuing capacity, see hire dedicated developers, staff augmentation and offshore software development.
See it applied
Each service page shows the process for that kind of project: MVP development, web application development, mobile app development and the rest, listed on custom software development.
Ready to start? Send the brief. You get a written scope.
Brief in. Scope out.
Tell us what you need. We will map out the approach, the stages and a written estimate.
Tell us about your project
Fill in the short form below. We will reply with questions or next steps and, once the scope is clear, a written estimate.
- Service area
- Worldwide (remote)