The studio
A studio, not an agency.
Kodedit researches how intelligent systems behave in real workflows, builds the software those workflows actually need, and then runs it. We take equity and ownership in what we make rather than invoicing for it and leaving.
01 — How it works
01
Research
We spend time where the work happens before we design for it. For MedSys that meant weeks in clinic corridors watching how a paper folder actually moves between a front desk, a consulting room, and a dispensary.
02
Build
We design and engineer the system end to end — interface, data model, offline behaviour, deployment. One team, no handoff between the people who studied the problem and the people who solve it.
03
Operate
We run the venture in production. Support, iteration, and uptime stay with us, which keeps the research honest: every wrong assumption comes back as a support ticket.
The three stages are not a pipeline we hand between teams. The people who sat in the clinic corridor are the people who wrote the dispensing queue and the people who answer when it breaks. That is the entire reason the model works.
02 — Principles
- 01
Research before code. Sit in the room where the work happens before designing for it.
- 02
Ship the whole system. A demo that skips billing is not a product.
- 03
Operate what we build. Ownership ends at uptime, not at handoff.
- 04
Earn the automation. Every automatic action must be inspectable and reversible.
- 05
Choose the unglamorous. The industries with the worst software have the most to gain.
03 — Who
Nokio Twumasi
Founder · Remote
Kodedit started from a narrow frustration: the software running clinics was worse than the software running coffee shops, and nobody seemed to find that strange. MedSys is the first answer. There will be others.
The studio is deliberately small. One team that can research a problem, design the system, ship it, and stay on the hook for it — because the alternative is a document handed to somebody who was not in the room.