We turn ideas and business problems into working software.

Marketplaces, business platforms, payment systems, automation and research infrastructure. We take the work from an unfinished problem through to something running in production — the data model, the backend, the interface and the deployment — and we take responsibility for all of it.

See what we have built How to work with us

We reply within one working day · contact@codelabpros.com

dale — auto-parts marketplace with escrow

The Dale marketplace, showing car parts listed with escrow protection

Dale — buyers pay, the money is held, the seller ships, the buyer confirms, and only then does the seller get paid.

What that meansevery line has a system behind it

The industry changes. The job does not.

Something needs to exist, nobody has fully worked out what it has to do, and it has to end up running in production where real people depend on it. That is the same work whether it is a marketplace, a fee platform or a research engine.

Products and marketplaces: Escrow, mobile-money checkout, seller payouts and three user-facing products in one platform.
Business platforms and SaaS: Fee collection for many schools at once, none of which may see another's books.
Payments and financial workflows: Reconciliation across three intake routes, duplicate handling, and a deliberate stop where the answer is ambiguous.
Automation and unattended software: An agent that researches businesses unattended, rejects most of them with a written reason, and will not act alone on three named things.
Data and research infrastructure: Every source preserved by a hash of its own contents, every conclusion attacked before it is relied on, and the refutations kept at the same weight as the findings.
Access, identity and audit: A permission model checked on the server for every route, and a record of every change with its before and after values, laid before a single business feature.

Built3 of 7

Three platforms real businesses run on, and a system built from nothing.

Two marketplaces and a business platform that people use to do their jobs, and a decision system built with no client and no brief. Nothing here is a mockup.

dalemarketplace.com

Dale

Payment systems

An auto-parts marketplace in Kenya with escrow built into the middle of it, not bolted to the side.

The difficult part: Money that belongs to neither party yet. Three separate products and two independently deployed services all have to agree about which state it is in, at every moment, including the minutes when only one of the two services has been redeployed.
Where it got to: Live, in productionTen months of continuous work alongside other engineers. The escrow lifecycle and the payout system behind it, a second delivery provider, fitment matching and the reporting engine are all in the product, and buyers, sellers and staff use it every day.
Our role: Engineer on the product team — backend and front-end

How it works →Visit the live site →

karo — reconciliation (illustration)Illustration

Karo

Payment systems

A fee platform for schools that replaces the manual matching of payments to pupils, and the arguments about balances that follow from getting it wrong.

The difficult part: Money arrives three different ways and a school's records have to be right whichever door it came through. That includes when the same payment arrives twice, and when the only identifying detail is a reference somebody typed on a phone.
Where it got to: ShippedMoney arrives three ways: live, by file, by hand. All three reach the same answer through the same code. Ambiguous cases route to a person, not to a rule.
Our role: Architecture and payments

How it works →

neostrata.co.ke

NeoStrata

Business platforms

The internal platform a skincare clinic and distribution business runs on: patients, appointments, stock, orders, partners, invoicing and the workflows between them.

The difficult part: Building eight phases of platform in a single coherent system without any of them having to be reworked. Access, audit and money were laid first, because those calcify: every later module inherits them, and retrofitting them across ninety screens is not a refactor, it is a rewrite.
Where it got to: Built and runningShipped in sequence: access and audit, clinic and client records, commerce and the B2B pipeline, a partner portal with multi-currency, multi-location, a workflow engine, a growth engine, and a business-performance layer.
Our role: Sole engineer — designed and built all of it

How it works →Visit the live site →

Range4 more systems

Data at scale, and software that runs unattended.

These are not the commercial argument. They are the evidence that the range behind it is real. All three were built with no client and no brief, which is the only way to find out what someone can do when nobody is scoping it.

zorevexa.com

Zorevexa

Automation

A direct-to-consumer supplement brand selling online, and the automation behind it that promotes the products, keeps three social accounts fed and routes customer questions to a person — with the whole thing driven and approved from Telegram, including an agent the founder can instruct to post on demand.

An hour a day comes back to the founder, and the automation cannot email a customer or post in public outside the fence it was given. What that avoids is the version of this that saves time until the morning it says something the brand has to apologise for.

Live, sellingHow it works →

qadi.io

Qadi

Payment systems

Official Python and TypeScript SDKs for a stablecoin payments API, and a local sandbox that lets a developer drive the whole payment flow without moving anything real.

A developer can learn the whole payment flow on their own machine and get it wrong as many times as they need to, without anything real moving. What that avoids is the first integration mistake being a real one.

Built and testedHow it works →

Prospecting agent

Autonomous systems

An agent that sources businesses, measures what is wrong with their websites, and decides which are worth approaching. Unattended, but not unsupervised.

Software that runs unattended and still cannot spend money, contact a real person or touch a live site without asking. The limits were written down before the capability existed.

Internal, runningHow it works →

cpos — research substrate

CPOS

Research infrastructure

Software plus a set of rules for investigating something without fooling yourself.

Research that records what it got wrong at the same weight as what it got right. The expensive kind of wrong is the kind nobody wrote down.

Research system, ran a real engagementHow it works →

Also shippedsites, not applications

hillsidegreen.com

Hillside Green

Marketing site

An agribusiness backing women-led SMEs into export

Capacity building, mentorship and market access for smallholder growers. The site carries services, partners, a blog and a gallery, and exists mainly to be credible to the development partners who fund that work.

Visit →

preemllc.com

Preem LLC

Corporate site

A government contracting and procurement firm

A contracting firm working across defence, energy and industrial supply in the Washington DC area. The site has to make a procurement officer confident enough to request a quote, so it leads with capability areas, industries served and delivery record rather than with the company's own story.

Visit →

All 7 systems, in depth →

How we worksix principles, all enforced in code

Six things we do, and what each one cost to learn.

Not preferences. Each one is enforced somewhere in running code, because a principle that depends on everybody remembering it is only a preference with good PR.

The whole method →

01Preserve the evidence, not your summary of itStore the source as it arrived. Summaries are a lossy answer to one question you happened to ask first.CIE and CPOS 02Corroboration is linked, never collapsedTwo sources saying the same thing is stronger evidence than one. De-duplicating destroys exactly that.CIE, across the whole corpus 03Measure the parameter, do not configure itA hand-written list is a guess wearing the costume of a decision, and it fails silently on the first input nobody anticipated.CIE, community calibration 04Attack every conclusion, especially the ones that look rightGo looking for the evidence against a claim before you rely on it, including the claims you like.CPOS-MKT-001 05Let unknown be an answerA system that cannot say 'we do not know' will say something else instead, and you will not be able to tell which it did.CIE opportunity scoring, and every proposal since 06Enforce it in code, or admit it is only an intentionA principle that depends on everyone remembering it is not a principle. It is a preference with good PR.Project Genesis, and one repository extraction

Working togetherprices published

Build something, join something, or examine something.

Three ways to buy the same capability, with prices. A price is the quickest way for either of us to find out this is not a fit. Each one also says what it does not include — that second list is where fixed-price work usually goes wrong.

BuildBuild Sprint$14,000Something specific that needs building properly, by one person who will take responsibility for all of it.4 weeks EmbeddedEmbedded Engineerfrom $7,500A team that needs an experienced engineer regularly, but not the cost or the wait of hiring one.monthly ReviewPayment Systems Audit$6,500A team already handling real payments, who wants to know what will break before it does.2 weeks

Noteseach one names the system it came from

September 2026The complaint you hear costs a morning. The one you do not costs the contract.Complaints arrive ranked by how annoying something is, never by what it costs. We counted 274,676 posts from business owners to see how far apart those two orders run.3 min September 2026What business owners actually describe when they describe a problemThe most common thing in 274,676 posts was not a technology request. It was a person doing something a computer should be doing. Almost nobody calls that a software problem.3 min September 2026They ask for AI. They are paying people to retype things.Two of the businesses in the corpus are paying seven salaries and a fulfilment chase to move data between systems that will not talk. Neither of them needs a model. We removed Hacker News to check the ratio was not an artefact, and it held.3 min September 2026We pointed our own research engine at our own marketWe built a system to find out what business owners say about their own companies. This month we used it on the things we get hired to build, and one answer reversed an assumption we had been working from.2 min September 2026You refund what you cannot proveAlmost nobody asks for a record of who changed what. Nought point one two per cent of 274,676 posts. Then a customer disputes what they were told, nobody can say, and you concede.2 min

All writing →

Tell us what you are trying to build, or what is going wrong with the thing you have.

A few paragraphs is plenty. You do not need a specification to start a conversation. Available for contract work, ongoing engagements and senior roles. We reply to everything within one working day, including the ones we turn down.

Send us the problem contact@codelabpros.com