Written before code.
The outcome, the systems touched, the approval point and the limits are agreed in writing before development starts. If the scope changes, the brief changes first.
About
A small studio, and the person who builds it
Fortoxa designs and builds agentic workflows for teams whose work crosses systems, approvals and audit. The same engineer scopes the work, writes it and hands it over.
01 / How we work
Small studio.
Small studio.
Direct accountability.
Fortoxa is run by Ismail, a senior full-stack engineer who scopes, builds and hands over the work himself. You talk to the person writing the code — there is no account layer and no junior handoff.
Working software weekly.
You review progress in your own repository, against real inputs. Test evidence covers what happens when a step fails, not only the happy path.
Nothing held hostage.
Code, configuration, run notes and the rollback plan are yours. Maintenance is optional, and it is priced like any other work.
03 / How we workA clear path from idea
A clear path from idea
to handover.
Know what happens next, what you receive and where your approval is needed.
- 01 / Define
Agree the outcome.
Map one task, the systems involved and the limits. Agree the scope and estimate before work starts.
You receive a written brief. - 02 / Build & review
See the work develop.
Review the implementation in your repository. Test the agreed behaviour, including what happens when something fails.
You receive code and test evidence. - 03 / Launch & hand over
Keep control after launch.
Approve the release with a rollback plan. Document how it runs, what remains open and who maintains it.
You receive release and handover notes.
03 / Limits
What we
What we
do not do.
Saying no early is part of the service. These are the requests we turn down, because they tend to end with a system nobody owns.
Out of scope
- Staff augmentation or a body-shop retainer.
- Speculative prototypes with no named owner or approval point.
- “AI strategy” decks with no working software behind them.
- Anything that needs an autonomous agent to act without a human approval step.
If your problem is adjacent to these, say so in the enquiry — there is usually a smaller, honest version of it worth building.
Next step
Tell us the task
Tell us the task
that keeps coming back.
One page is enough: what happens today, the systems involved, who approves the result.
Four questions, one page. The enquiry goes to the studio workflow and we reply by email within one working day.