S/07 · Services
Back offices & CRMs
The tools your team opens every morning.
Admin panels, CRMs and internal tools shaped around how your team actually works: fast tables, clear pipelines, the right permissions and the busywork automated away.
- Built for
- Your workflow, not a template
- Includes
- Roles, audit logs, automation
- Connects to
- Your API and existing tools
- 01
Your team lives in spreadsheets and copy-paste.
- 02
Off-the-shelf CRMs force you to work their way.
- 03
Nobody can tell who changed what, or when.
- 04
The same tasks get done by hand every single day.
- D/01
Fast data tables
Most of a back-office day is spent in tables, so we make them fast and forgiving. Search, filters and sorting run on the server and answer in milliseconds, saved views keep each person’s usual filters a click away, and bulk actions and exports work on exactly what is on screen.
Included
- Server-side search, filters and sorting
- Saved views for each person and each team
- Bulk actions, with an undo where it is safe
- Excel and CSV export of exactly what you filtered
admin · bookings · 1,284,902 rows · 38 ms ID Status Clinic Slot Payment #10482 Confirmed North branch Mon 10:30 Paid #10481 Pending City centre Mon 11:00 — #10479 Cancelled North branch Sun 16:15 Refunded #10478 Confirmed West branch Sun 15:00 Paid #10476 No-show City centre Sun 09:45 Paid - D/02
Pipelines
We model the stages your work actually goes through, whether it is a lead, a support ticket or an order, with the rules for moving between them. Everyone sees what is waiting on them, and managers see where work piles up before customers notice.
Included
- Stages and the rules for moving between them
- Board and list views of the same work
- Reminders for anything stuck too long in a stage
- Conversion and time-in-stage numbers per stage
admin · sales pipeline · this month New leads
42
+9 on last week
Contacted
31
first reply in 3 h on average
Proposal sent
12
4 waiting over 7 days
Won
8
26% of qualified leads
- D/03
Roles & permissions
Access is designed around roles that match your organisation, down to individual actions and, where it matters, individual fields. Each person gets what their job needs and nothing more, which protects your data and keeps mistakes small.
Included
- Roles that match your team, not a fixed set
- Permissions per action, and per field where needed
- Access limited to a branch, a region or a person’s own records
- A table of who can do what, kept with the code
admin · roles Permission Admin Manager Reception Doctor View bookings ✓ ✓ ✓ Own only Edit bookings ✓ ✓ ✓ — Issue refunds ✓ ✓ — — Export reports ✓ ✓ — — Manage users ✓ — — — Read medical notes — — — ✓ - D/04
Audit trail
Every change is recorded with who made it, when, and what the value was before, along with every attempt that was refused. When a number looks wrong or a customer disputes something, you find the answer in a minute instead of asking around the office.
Included
- Before and after values for every change
- Refused attempts, not only successful ones
- Filters by person, record and date
- Records that cannot be edited, kept as long as you need
admin · audit log $ filter: last hour · 6 of 214 events
10:41:07 sara booking #10482 status pending → confirmed
10:39:52 reza patient #8812 phone ***41 → ***07
10:35:10 system invoice #3307 created by rule overdue-7d
! 10:22:44 ali refund #219 over limit, approved by manager
× 10:18:03 nima export bookings denied: no permission
- D/05
Automation
The tasks your team repeats every day are turned into rules that run on their own: reminders, follow-ups, assignments and reports. Each rule is written in plain language, can be paused by an admin, and leaves a record of every time it ran.
Included
- Scheduled and event-driven rules
- Plain-language rules your admins can pause
- A run history, with alerts when a run fails
- Templates for email, SMS and PDF documents
automations · today 07:00
Overdue invoices
→ 14 reminders emailed
08:30
Tomorrow’s appointments
→ 212 SMS reminders sent
09:00
New leads assigned
→ shared between 3 agents
18:00
Daily report
→ PDF to the managers’ inbox
- D/06
Integrations
The back office becomes the one place where a customer’s whole story lives: their emails, messages, calls and invoices, next to their record. We connect the tools you already use instead of replacing them, and every connection retries and reports when something on the other side is down.
Included
- Email and SMS sending, with delivery status
- Calls and recordings on the customer record
- Accounting sync for invoices and payments
- Webhooks and an API for your other systems
docs/integrations.mmd
- 01
Shadow the team
We watch how the work really gets done before designing a single screen.
- 02
Design the flows
Pipelines, screens and permissions agreed with the people who will use them.
- 03
Build iteratively
Small releases the team uses straight away, shaped by their feedback.
- 04
Train & hand over
Short training, written guides and support while the team settles in.
Your team usually starts using the first part within four to six weeks, and the rest arrives in releases every two weeks. A complete back office typically takes ten to fourteen weeks, shaped all the way by the people who use it.
- Week 1
We sit with your team, watch how the work is done today, and collect the spreadsheets it runs on.
- Week 2
Flows, screens and permissions agreed with the people who will use them.
- Weeks 3–6
The first module goes live, with your existing data migrated and cleaned.
- Weeks 7–12
Pipelines, automation and integrations, in releases every two weeks.
- Weeks 13–14
Training for each role, written guides, and support while the team settles in.
The source code and database
The whole system in your repository and on your servers, with instructions to run it.
Your data, cleaned up
Everything migrated from spreadsheets and old systems, with duplicates merged and gaps marked.
The roles and permissions map
Who can see and do what, written down and kept next to the code.
Guides for every role
Short written guides and recorded training sessions for each part of the team.
The automation rules
Every rule written in plain language, so you know what runs and when.
A check-in after the first month
We review how the team is using it and adjust the screens and rules that slow them down.
- Next.js
- TypeScript
- Go
- PostgreSQL
- Role-based access
- Audit logs
- Webhooks
- Excel import / export
Why not just use an off-the-shelf CRM?
Often you should, and we will say so. Custom pays off when your process is your advantage or the off-the-shelf tool is costing you more than it saves.
Can you migrate our existing data?
Yes — spreadsheets, old databases or another CRM, cleaned up on the way in.
Can it connect to our phone system?
Yes. Calls, recordings and caller details can live right next to the customer record.
How long until the team can use it?
The first part is usually in daily use within four to six weeks. The rest follows in releases every two weeks, so the team never waits months for something to try.
What do you need from our team?
A few hours in the first week to watch the work being done, one person who can make decisions about the flows, and honest feedback on each release.
Tell us what you are building.
Every project starts with a consultation: you bring the idea and everything you know, we turn it into a design you can build on.
Book a consultation