Nine disciplines that keep meeting in the same projects.
Most engagements start in one of these and touch two or three. A process automation reveals an integration gap; an integration gap turns out to need a small application. They are listed separately for clarity, not because they arrive that way.
Build the software
Applications, integrations and hardening, for when configuration runs out.
Custom Software Development
Production web applications and internal tools (ERP, portals, dashboards, PWAs) built on Next.js and Postgres, deployed on infrastructure you own.
- Systems that fit the process
- Permissions that hold
- Nothing is really deleted
- Installable and offline-capable
- Next.js
- React
- TypeScript
- +5 more
Systems Integration & APIs
Two-way syncs, webhook pipelines, parsers and internal APIs that move data between platforms reliably, including the ones with no native connector.
- One record, one home
- Retries that do not duplicate
- Custom connectors
- Legacy data recovered
- REST
- Webhooks
- OAuth
- +5 more
Vibe-Coded App Rescue & Production Hardening
Built an app with an AI coding tool? We audit it, close the security and reliability gaps, and take it to production, or tell you plainly when a rewrite is the cheaper road.
- A straight assessment first
- Access that is actually enforced
- Fails safely, recovers quickly
- Code someone can maintain
- Next.js
- React
- TypeScript
- +5 more
Put AI to work
Models and agents inside real pipelines, with humans on the irreversible steps.
AI Engineering & Integration
Document understanding, extraction, classification and drafting wired into the systems you already run, with review steps, fallbacks and cost control designed in.
- Document capture that people trust
- Provider redundancy by default
- Humans on the irreversible steps
- Cost you can see
- Claude
- Claude Code
- OpenAI
- +5 more
Claude Code Development & Team Setup
Custom software built with Claude Code under engineering review, and Claude Code set up for your own team: project rules, permissions, tests and a review process that keeps the speed without the surprises.
- Speed without unread code
- A codebase the agent understands
- Permissions that match the risk
- Your team able to carry on
- Claude Code
- Claude
- MCP
- +5 more
MCP Server Development
Model Context Protocol servers over your internal data and tools, built read-only first, with the same permissions, review steps and audit trail as the rest of your software.
- One governed doorway
- Read-only first
- Your rules still apply
- Narrow by design
- MCP
- Claude
- Claude Code
- +4 more
Automate the operation
Processes, scenarios and the platforms your team opens every morning.
Business Process Automation
Map the process as it really happens, then rebuild it so the handoffs, approvals and data entry happen on their own, with an audit trail you can defend.
- Intake that fills itself in
- Approvals with a paper trail
- SLA clocks and escalation
- Rules the database enforces
- Make.com
- Zapier
- n8n
- +5 more
Workflow Automation
Scenario design, rebuilds and rescues on the major workflow platforms, plus self-hosted runners for when the operations bill or the platform's limits stop making sense.
- Scenarios that fail loudly
- Operations under control
- Secrets out of the blueprint
- An exit route
- Make.com
- Zapier
- n8n
- +5 more
Ops Platforms & CRM
Board and base architecture, CRM implementation, and the automations, portals and integrations that turn a licence into an operating system.
- A schema that survives growth
- External portals without seats
- Reporting that answers the question
- Documents in, records out
- monday.com
- Airtable
- HubSpot
- +5 more
Not sure which you need?
Most projects touch two or three of these. Describe the problem and we will tell you where it fits.
Five phases, and the riskiest part built first.
Mapping and proving are short on purpose, so a wrong assumption surfaces in week two.
- 01
Week 1
Map
We trace the process as it is actually performed, including the workarounds, the exceptions, and the step that exists only to correct an earlier step. This is where a bad idea gets caught, before it is expensive.
- 02
Weeks 2–3
Prove
The riskiest assumption gets built first and put in front of real data. If a document parser cannot read your actual documents, that is worth discovering in week two.
- 03
Weeks 3–8
Build
Delivery in reviewable increments on your own repository and your own infrastructure. Constraints go in the database, credentials go in environment variables, and everything that writes leaves an audit entry.
- 04
Weeks 8–10
Cut over
New and old run side by side, with the new path logging what it would have done. Comparing the two on real work is what makes go-live uneventful.
- 05
Ongoing
Hand over
You own the repository, the accounts and the deploy path from day one. Whether we stay on for changes is your decision.
Deep in a few things, rather than shallow across everything.
Five groups, all of them run in production every week.
- 01
Automation platforms
Where the workflows live, and where we rescue them when they break.
- 02
Ops platforms & CRM
The systems your team opens every morning.
- 03
AI & agents
Models put to work inside real pipelines, with humans on the irreversible steps.
- 04
Product & platform
What we reach for when the software has to be built rather than configured.
- 05
Data & infrastructure
Postgres, mostly, with the rules kept in the schema where they belong.
- Supabase
- PostgreSQL
- Row-level security
- pg_cron
- Vercel
- Edge Functions
Tell us about the process that keeps costing you.
A 15-minute call is usually enough to say whether this is an automation, an integration, or something that should be built, and whether we are the right people for it.
What happens on the call
- 15 minutes, no deck
- We map the process on the call
- A written scope, or an honest no