Engineering scale. Engineering growth.

An engineering partner for teams anywhere in the world: we build production software and stay on to run it. Scale for enterprises whose systems have to hold up under real traffic and real money. Growth for startups that need to ship this quarter and keep shipping.

Trusted by teams in payments, crypto, media, travel and hospitality.

02

No surprises. That's the whole method.

Every engagement produces documents, not just code. That isn't bureaucracy. It's how you stay in control of something you didn't build yourself.

Remediation report

Illustrative example
Client
Withheld
Severity
High
Status
Closed
  1. Root cause

    A provider timeout triggered a retry that wrote some payments twice.

  2. Fix shipped

    Every write now carries an idempotency key, so a retry cannot duplicate it.

  3. Regenerated or reconciled

    The duplicate entries were found, reversed and checked against the provider's statement.

  4. Needs a decision from you

    Whether to tell the affected customers, and what to say.

One for every incident. Routine work goes on the monthly statement.

  1. Brief and PRD

    You tell us what you need, in your own words. We write back a PRD: what's in, what's out, the shape of the system, and what we're not sure about yet. Nothing gets built until you've signed it.

  2. Build in the open

    When something you depend on changes, you get a change notice before it ships: what changed, why, what to do, and by when. Your mobile team gets the same note we'd write for ourselves.

  3. Run with reports

    When production breaks, you get the root cause, the fix, what was regenerated or reconciled, and what still needs a decision from you, in a written remediation report. Not a Slack thread.

03

Why teams stay.

  • The people who build it are the people who run it.

    No handoff to an ops team that has never seen the code. The engineers who shipped your system are the ones watching it in production.

  • You get paper, not promises.

    A PRD before we start, change notices while we build, remediation reports when something breaks, and a clear statement every month.

  • We use what we sell.

    This site runs on Reoclo and sends its mail through Prawnwire, the two businesses we started because client work needed them. We run them every day.

  • We say the uncomfortable thing early.

    If the brief asks for the wrong thing, you'll read that in the PRD, not find out after launch.

04

Two businesses, so far.

We started Reoclo and Prawnwire because client work needed them: a control plane for the servers we run, and email we could trust. Each is now a business of its own, with its own site, terms and sign-up, and Boxmarshall still builds and runs both. They lean on each other too: Prawnwire runs on Reoclo, and Reoclo sends its mail through Prawnwire.

05

Some things we've handed over.

Names withheld. The details are what matter.

  • Fintech companies

    More than one of these started the same way: a security audit of the entire stack, written up with what we found and a path to fixing each item. Each time, we were hired to do the fixing, then put on permanent retainer on the strength of the work. Disaster recovery followed the same arc: audit, fixes, retainer.

    Handed overAudit reports, the fixes, and a permanent retainer.

  • Payments company

    We host and operate their production and staging with offsite backups under an annual SLA, on a fixed monthly retainer. They think about their product. We think about the servers.

    Handed overProduction they don't have to think about.

  • Hospitality company

    They needed to turn interest into customers: capture leads, reach them by email, meet them on mobile. We built tailored websites, put their business email on Prawnwire, and shipped a mobile app MVP. They capture users now, and sales have improved.

    Handed overWebsites, mailboxes on Prawnwire, and an app MVP.

  • Media platform

    We built the publishing platform behind two titles, then stayed on to host it and run its email campaigns.

    Handed overThe platform, hosting, and campaigns on one monthly statement.

07

Questions we get asked.

Straight answers. If yours isn't here, ask us.

What happens first?

You send us a brief in your own words. We write back a PRD: what's in, what's out, how the system or site will be shaped, and what we're unsure about. You mark it up, we revise, you sign it off. Then we build against it.

How do you price work?

Two ways. Fixed scope for work with a clear end, like a site, an integration or a launch. A monthly retainer for ongoing engineering or for running your infrastructure. The contact form has budget bands in US dollars and in naira.

Can you just run what we already have?

Yes. Managed infrastructure is its own service: production and staging servers, offsite backups, monitoring, incident response and an annual SLA, on a monthly retainer. We'll read the code before we agree to be on call for it.

What happens when something breaks?

You get the root cause, the fix that shipped, what was regenerated or reconciled, and what still needs a decision from you, in a written remediation report. Routine work shows up on a monthly statement, not as a surprise.

Do you work with teams in other countries?

Yes. We work with international clients and we meet you where you are. Every client has a named project lead who is available as you need them. Because everything is written down, we also work well asynchronously: nobody has to be awake at the same time to know what's going on.

Where does our software run?

On servers you own or rent, with any provider, managed through Reoclo. Nothing is locked to us: the servers are yours.

Who owns what you build?

You do. It's written into the engagement terms you sign before we start.

Do you do design?

For websites, yes, with our design partners. You approve a lookbook before any code is written. For product work we design the system and the screens with you, and bring in a partner when a project needs more visual design than we should be doing ourselves.

Let's build something you won't have to worry about.

Tell us what you need to build or keep running. We reply by email, usually within one business day.