AutomationAI adoptionSoftwareNairobi

The technical team
you don’t have to hire.

Tell us the business problem. We work out what should be built, build it, run it afterwards, and tell you when the honest answer is to build nothing at all. No job specs, no engineering salaries, no managing people whose work you can’t assess.

For businesses that don’t have an engineering department — and would rather not build one. Based in Nairobi, working across Kenya and remotely beyond it.

01 — Sound familiar?

Every one of these is a job nobody was hired to do, being done by someone who was hired to do something else.

02 — What we handleIn detail →
03 — Versus the alternativesHonestly, including where they win
Hiring in-houseA typical agencyTesseract
Time before anything happensThree to six monthsA few weeksDays
What it costsSalary and overhead, every monthProject fee, then a support contractScoped work, only when you need it
Who manages the technical workYou doTheir project manager, billed to youNobody — that is the point
Who is there in month sixWhoever has not leftNobodyUs. We run what we build
When the need changesRetrain or rehireA new statement of workWe already know the system

Hiring wins when the work is permanent and large enough to fill a role — we’ll say so if that’s your situation. An agency wins when you already have someone technical to hold them to account.

04 — Before you spend anything

Should you automate it at all?

Ten questions about one process. You get an honest answer — includingno, which is right more often than anyone selling technology will admit. Runs in your browser; nothing you answer reaches us.

Run the diagnostic →
05 — One of oursAll work →

Inkmark · Printing, embroidery and engraving · Nairobi, Kenya

Replaced a mockup-by-email approval loop with a design studio customers use themselves.

Every order began the same way. A customer sent a logo by email or WhatsApp and described where they wanted it — "centred on the chest, about the size of a fist". Someone at Inkmark interpreted that, produced a mockup, and sent it back.

Read what changed →
Before this, every job started with someone describing where they wanted their logo and us guessing what they meant. We would send a mockup, they would ask for it bigger, we would send another. Two or three rounds before we could even quote the job. Now the customer places it themselves and approves the thing they are actually going to receive. The arguments about size and position have stopped, and so have the reprints we used to absorb.
FelixFounder, Inkmark
06 — How we work, in publicAll 12 tools →

Most of what we build belongs to the client, so we run our own in the open instead: 12 tools, free, no account, nothing uploaded — built to the standard we would ship you, and running on the same infrastructure.

Open one. Read how it behaves, what it refuses to do, and what it tells you when you give it something malformed. That is a more honest sample of how we build than a logo wall.

zsh
❯ curl tesseract.page

  TESSERACT
  Your technical department · Nairobi, Kenya
  ────────────────────────────────
  tools    tesseract.page/tools
  email    info@tesseract.page

This page returns plain text to anyone asking from a terminal. Same URL, different answer — which is the whole job in miniature.

07 — Start here

What would you stop doing by hand?

Six questions about the problem — in plain language, no technical detail needed. Fixed scope, fixed price, and it goes straight to us.

Tell us the problem →
Esc