How we work
A written scope first, and you pay as it works.
Most first projects are scoped in writing within 48 hours, with phased payment. No surprise invoices: you see a written scope before you pay anything.
A person replies within 1 working hour. No payment, no PIN, no obligation.
What does working with Techmode involve?
A Techmode project runs in four phases. Discover maps and times your current process and produces a written scope. Design puts the thing in front of you before it is built. Build ships a working version every one or two weeks. Grow launches it, hands over every account, and measures against the baseline. You pay a small deposit, then milestones, and the balance only after you have used the system on your own phone.
The four phases
Discover, Design, Build, Grow.
Discover
We walk your process with the people who do the work, and time the slow steps.
A working session with the people who actually do the work, not only the person paying for the project. We walk the process, time the slow parts, and write down where the hours and the money are going. Most of what we find is not what the brief said, which is the point. By the end of it we can tell you which single change is worth making first — and occasionally that the answer is to simplify a process rather than build anything.
- A one-page map of the current process, with the slow steps timed
- A recommendation on what to do first, and why that one
- A written scope: what is being built, and what is explicitly not
- A fixed price and a delivery date against that scope
What we need from you: Half a day, and access to the people who do the work rather than a summary of it.
Design
You click through the screens, or read the flow step by step, before anything is built.
You see the thing before it exists. For a site or an app that means screens you can click through on your own phone; for an automation it means the flow written out step by step, including what happens when a step fails. Changing a screen at this stage costs an afternoon. Changing it after the build costs a week, which is the entire reason this phase is not skipped.
- Clickable designs at real screen sizes, on your device not ours
- The flow for every failure case, not just the happy one
- Agreed copy for anything a customer will read
- Your sign-off, in writing, on what gets built
What we need from you: A review session and one round of consolidated feedback, from someone who can decide.
Build
We build in one- or two-week cycles, and each one ends with a link you can open.
Work happens in one- or two-week cycles, and at the end of each you get a working link or a build on your phone. There is no long silence followed by a reveal. We test against the conditions your customers are actually in — a mid-range Android on mobile data, not a laptop on fibre — and anything that has to handle money is tested against real failure cases before it goes near a customer.
- A working version at the end of every cycle, on a link you can open
- A short written note each cycle: what shipped, what is next, what changed
- Testing on real devices and a throttled mobile connection
- Accessibility and performance checked as we go, not audited at the end
What we need from you: About an hour a week to look at what shipped and say if it is wrong.
Grow
We launch, stay through the first month of real use, and hand over every account.
We launch, then stay long enough to see the first month of real use, because that is where the edge cases live. You get every login and account handed over, the documentation to run it, and training for whoever will own it. After that, ongoing support is your choice and is scoped in writing like any other work. You own the code and the accounts either way.
- Launch, plus a supervised first week where someone is watching
- Every credential and account handed to you
- Documentation and training for the person who will own it
- A measurement against the baseline we timed in Discover
What we need from you: A named owner on your side, and an hour for the handover session.
How we price
What is true of every project.
The scope is written before the work starts
You get a document listing what is being built and what is explicitly not. Anything outside it is a change with its own price, agreed before it happens.
Payment is phased against delivery
A small deposit, a payment at each milestone, and the balance only after you have used your system on your own phone. You are never paying for work you have not seen.
You own what we build
The code, the domain, the hosting accounts and the data sit in your name from day one. Ongoing support is a service you can stop, never a hostage arrangement.
Third-party costs are yours and are named up front
Hosting, WhatsApp message fees, app store accounts, SMS credit. We estimate them against your volume before you commit, and they are billed to you, not marked up by us.
How payment works
Four steps, and the balance comes last.
What you hold, and what you have paid
- You hold
- The written scope: what is built, what is not, and the weeks it takes.
- You have paid
- Nothing.
- You hold
- The scope you approved, and work that has started.
- You have paid
- A small deposit.
- You hold
- Each working part delivered so far, checked by you.
- You have paid
- The deposit, and the milestones you have checked.
- You hold
- Your system, used on your own phone, with the code and accounts in your name.
- You have paid
- The balance, last of all.
Step 1 of 4
Free written scope
Within 48 hours of the walkthrough call you get the scope: what is built, what is not, and the weeks it takes. You pay nothing for it.
Step 2 of 4
A small deposit
When you approve the scope, a small deposit starts the work.
Step 3 of 4
Milestone payments
As each working part is delivered, you check it and pay that milestone.
Step 4 of 4
The balance, last
You pay the balance only after you have used your system on your own phone.
Six guarantees
What you can hold us to.
See it working before you pay the balance.
Payments follow milestones: a small deposit, then the balance only after you have used your system on your own phone.
The scope is free and yours.
If you don't go ahead, keep the written scope and use it with anyone.
30-day fix promise.
Anything in scope that breaks in the first 30 days after launch is fixed free.
You own everything.
Code, domain, hosting, WhatsApp and Paybill accounts sit in your name from day one.
We never ask for your PIN.
No M-Pesa PIN, no passwords in chat.
We tell you before we're late.
If a date will slip, you hear it from us first, with the new date and the reason.
How we handle your data is on security.
Your written scope
Tell us what you need. We scope it in writing.
Answer four quick questions and see where a first phase would start and how many weeks it usually takes. Then ask for your written scope: within 48 hours you get what is built, what is not, the weeks it takes and how payment is phased.
Questions
How a project runs, answered.
Do you charge for the first conversation?
No. The first conversation is free, and you owe us nothing after it. If the honest answer is that you should simplify a process rather than build anything, that is what we will tell you, and it costs you nothing to hear it.
How does payment work?
Phased against delivery: a small deposit when you approve the written scope, a payment at each milestone, and the balance only after you have used your system on your own phone. You are never paying for work you have not seen running.
Who owns the code you write?
You do. The code, the domain, the hosting, and the WhatsApp and Paybill accounts sit in your name from day one, and the data is yours too. If you later move to another team, the written handover exists for exactly that. Nothing is locked to us.
What happens in the first week?
A working session with the people who do the work, in your office where possible. We walk the process, time the slow steps, and leave with a map. Within 48 hours of it you get a written scope, a fixed price and a date.
How involved do we need to be?
Heavily in week one, then about an hour a week. The first week is where your input changes the outcome; skimping on it is the most reliable way to get the wrong thing built well.
What if we want to change something mid-project?
Small changes inside the agreed scope are absorbed. Anything larger is quoted as a change before it happens, so it never arrives as a surprise on the invoice. Nothing is refused outright — it is priced and you decide.
What if it does not work?
You see working software at the end of every cycle, so there is no point at which the project could quietly be failing without you knowing. Payment is phased against those deliveries, and the scope you signed is the standard we are held to.
Do you work on site or remotely?
The first walkthrough and the training are best done in person, and we are in Westlands, so for Nairobi clients that is usually a meeting. The build itself is remote, with a working link at the end of every cycle.
What happens after launch?
We stay for the first month of real use, hand over every account and credential, and train the person who will own it.
Start step one. The scope is free and yours to keep
Tell us what slows your business down. After a short call, you get a free written scope within 48 hours, with the weeks it would take.
A person replies within 1 working hour. No payment, no PIN, no obligation.
Prefer direct? [email protected] · +254 731 290 928 · Mon–Sat, 8 am–6 pm EAT