Skip to content
Techmode.

How we work

Four phases, and no black boxes.

You see working software at the end of every cycle, you know the price before we start, and you own everything at the end. Here is exactly what that looks like.

What does working with Techmode involve?

A Techmode project runs in four phases. Discover maps and times your current process and produces a fixed 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.

The four phases

Discover, Design, Build, Grow.

  • Discover

    We learn your business, map the bottlenecks, and agree on the wins that matter most.

    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

    We prototype the solution — flows, screens, or automations — so you see it before we build it.

    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

    Our team ships in fast iterations, keeping you in the loop the whole way.

    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, measure, and optimize — turning the solution into compounding results.

    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 a care plan is available and optional — you own the code and the accounts whether or not you take one.

    • 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.

What you can hold us to

Four commitments, in writing.

We are a new agency, so asking you to take our word for it is not an argument we are entitled to make. These are the structural answers instead.

01

A written scope, before any money moves

You know what is being built and what is not. Anything outside it is a change with its own price, agreed before it happens rather than invoiced after.

02

Payment phased against delivery

A deposit, milestones, and a balance at handover. You are never paying for work you have not seen running.

03

You own everything

Code, domain, hosting accounts, data. Handed over at launch, whether or not you keep us on afterwards.

04

We will tell you when not to build

If the discovery session shows the process should be simplified rather than automated, that is what the recommendation will say. It costs us a project and saves you one.

Starting prices and what moves them are on pricing, and how we handle your data is on security.

Questions

How a project runs, answered.

  • 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 a few days 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?

    Discovery and 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. A care plan from KSh 15,000 a month is available and entirely optional.

Ready for software that wins you customers?

Book a free, no-obligation consultation. We'll map your fastest wins and show you exactly what's possible — in plain language, with clear numbers.

Prefer direct? [email protected] · +254 731 290 928 · Mon–Sat, 8am–6pm EAT

WhatsAppBook a call