Fewer manual stepsbetween decisions
We map how work really moves through your team — the spreadsheets, the WhatsApp forwards, the approvals that wait on one person — and replace the repetitive middle with workflows that are monitored and easy to change. AI is used where its output can be checked, with a person in the loop where it can't.
- Typical length
- 2–8 weeks
- Best for
- Operations teams buried in repetition
- Pairs with
- Web & software development
What's included
Every engagement is scoped from these parts. We'll tell you which ones you actually need — and which you don't.
Process mapping
The real workflow documented, including the steps nobody admits to.
Approval routing
Requests reach the right person with the context attached, and nothing waits in an inbox.
Notifications
Email, SMS or WhatsApp at each status change, sent from database events so none are missed.
Integrations
Connect the tools you already use — email, SMS, WhatsApp, spreadsheets and accounting software.
AI steps
Classification, extraction and drafting with Claude, behind checks and a human gate.
Audit trail
Every automated action logged, attributable and reversible.
Tools we reach for, and why
The stack is boring on purpose. It has to be maintainable by whoever inherits it, including a team that has never met us.
Postgres triggers
Events fire from the data itself, so a notification can't be forgotten.
Email & SMS APIs
Messages reach people in the inbox or on the phone they already check.
Edge functions
Small, secure jobs that scale to zero when idle.
Claude API
Reliable structured output for classification and drafting.
How a project runs
You see working software early and often. Every stage ends with something you can review, not a status update.
- Stage 1
Discovery
We learn your goals, your users and your constraints, and write down what we think the problem is. If we disagree with the brief, you hear it here.
Problem statement and success measures
- Stage 2
Plan
A written plan covering scope, data model, roles and what ships first, with a fixed price for the next phase.
Scope, architecture and quote
- Stage 3
Build
Short design and build cycles. Every week ends with a working version you can click through, not a status update.
Weekly demo on a live preview link
- Stage 4
Launch and grow
We ship, monitor and keep improving — or hand everything over with documentation and a walkthrough for your team.
Production release, docs and handover
Common questions
About automation & ai with Pixelspective.
That isn't the aim. We automate the copying, chasing and re-keying so your people spend their time on judgement and customers.
Usually, yes. If a tool has an API or sends email, we can connect it. We'll check what's possible during discovery, before you commit.
We only use it for steps whose output can be validated, log every decision, and keep a person approving anything that matters.
Is this the right piece of work?
Send two paragraphs about the problem. We'll reply with how we'd approach it and a rough shape for scope and cost — or point you somewhere better suited.
Every brief is read by Mark Okutu, founder and lead developer, and he replies to each one personally.
Prefer email?
pixelspective1@gmail.com