About ◆ The name

A trace is the mark that remains

An imprint, an effect — what is left after you have gone. It is also what we are hired to leave behind.

Three readings, three commitments

Most businesses need similar skeletons — accounts, orders, approvals, dashboards. What makes a system theirs is how it is shaped around their people, their tools and their workflow. That shaping is the mark it leaves.

TRACE builds the skeleton properly, then places the mark. We started because too many companies were paying for templates with their logo on top, or for developer hours with nobody accountable for the result.

We are a US-facing studio with our engineering team in Cairo. Our mark is three nuqtas — the Arabic word for the dots that turn one letter into another — a nod to where we build. You get senior engineers who overlap your working day, a fixed price per phase, and everything we build handed over to you.

Trace
We study how work actually moves
Discovery before design. We sit with the people in the warehouse, the clinic, the office — before we quote.
Imprint
The result is uniquely yours
Custom, shaped to the workflow and the tools you already pay for. No templates with your logo on top.
Effect
It changes something measurable
We measure before and after, and we say the number — even when it is smaller than we hoped.

How we work

Discovery before a line of code
We map how the work moves before anyone writes code, and you get the scope in writing.
Your tools, not ours
We work in the tools you already use — Slack, GitHub, Jira, Linear.
Fixed price per phase
Stop after any phase and keep everything we built up to that point.
Measured, then handed over
Source code, designs, documentation and accounts are yours.

Who you will be talking to

Founder
Product & delivery
Runs discovery, writes the scope, stays on your Slack channel.
Lead engineer
Architecture
Owns the stack, the handover and the code you end up with.