Services
Four things we do well, and the one way we do all of them.
Product and backend engineering
We design and build the systems your business runs on, from the API to the screens, and we make them hold up under real traffic and real money.
Engagement Fixed-scope project or monthly retainer.
Includes
- APIs and services
- Web applications
- Mobile applications, with partners where needed
- Third-party integrations: KYC providers, payment rails, messaging
- Security hardening: authenticated webhooks, idempotent processing, PII-safe logging
- A change notice for every breaking API change
Managed infrastructure
Your production stack, operated by the people who built the tooling to operate it. You get servers that are patched, backed up, and watched, and a written account of anything that goes wrong.
Engagement Monthly retainer.
Includes
- Production and staging servers
- Offsite backups
- Deployments through Reoclo
- Monitoring and incident response
- Written remediation reports
- An annual SLA
Websites and launch sites
A site that says what your company is, built the same way we build everything else: a written brief, a PRD you sign off, a lookbook you approve, then the build.
Engagement Fixed-scope project.
Includes
- Corporate and brochure sites
- Waitlist and launch sites
- PRD first, lookbook for sign-off, then the build with our design partners
- Hosting and mailboxes if you want them
Email and communications
Email that lands. Mailboxes for your people on Prawnwire, campaigns for your audience through a campaign tool, and the DNS records that keep both out of the spam folder.
Engagement Monthly.
Includes
- Mailboxes on Prawnwire
- DNS onboarding (MX, SPF, DKIM, DMARC, MTA-STS) with a written guide for your DNS provider
- Newsletters and campaigns
- Deliverability monitoring
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.
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.
The brief is what you send us, captured verbatim. The PRD is what we write back: scope, what is in and out, the site map or system shape, functional requirements, and open questions, as a document you can mark up. Nothing is built until it is signed off, and the PRD is what the build is checked against.
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.
When an endpoint moves, a field changes shape, or a response is tightened, the people integrating with it get a change notice: what changed, why, what to do, and by when. Mobile teams, contractors, and your own developers all get the same document.
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.
When something breaks in production, you get the root cause, the fix that shipped, what was regenerated or reconciled, and what still needs a business decision, in a written remediation report. Routine operations show up as monthly statements, not surprises.
What you receive
Every engagement produces documents, not just code: a PRD you sign, change notices for anything that breaks an integration, incident and remediation reports, and invoices and statements you can read without calling us.
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.