What I take on
CRMs & Admin Desks.
Built by me, start to deploy
The internal screens your staff live in, built around what they actually do.
At Xaibridge these are the desks behind fintech, healthcare and operations teams, on an architecture carrying 1M+ users.
Why this gets built
Staff keep a spreadsheet open beside the product because the admin panel cannot answer the question in front of them. Every answer then becomes a message to an engineer.
What I build
- Per-person permissions: which routes someone can open and whether they can write there. No role tiers that stop matching the org after a month.
- Leads from the site, ads or WhatsApp landing in the pipeline directly, with an owner and a stage on each one.
- The screens staff use all day: queues, notes, the handoff from sales to support, and the ticket desk after a deal closes.
- Actions that leave a record. Who approved a payout, who re-opened an evaluation, who changed a price.
- Query cost treated as a feature. A desk that opens two thousand live listeners will freeze, and finding that out after launch is a rewrite.
How long it takes
About four weeks to a desk staff will open by choice.
Reporting and the permission map are the parts that keep growing after launch, so I build both to be changed without me.
What ships
- Admin desk and its permission map
- Pipeline with owners and stages
- Adapters from ads, forms and WhatsApp
- Audit trail on every staff action
- Reporting your team can edit without me
Tech stack
Next.jsTypeScriptNode.jsPostgresMySQLFirestoreRedis
Next step
Let’s talk, 30 minutesNeed this built?
Tell me what you’re running and where it breaks. Half an hour is usually enough for me to say what it takes and what I’d do first.
10 / 12