A lightweight tool that makes work visible across Christchurch + Group: quick daily check-ins, instant job capture, and clean summaries — without your team having to live in admin software. We build, host and maintain it; your team just runs it day-to-day, and your data stays in your own tools.
What we propose
Field staff stay in Slack
Check-ins and job updates happen with a tap in Slack — nobody has to open or learn another system.
One engine ties it together
An automation engine (n8n) routes everything between Slack, ClickUp and your data store — quietly, in the background.
Your own data store
Every check-in and job is stored in your own database (Supabase) — a real asset you own and can build on.
Clear summaries where you work
Daily + 6am summaries and a jobs-won board, posted straight into Slack — no new app to learn.
How it works
Goes in
📱 Slack — your team
- Start & end-of-day check-ins
- "Add a job" (call/email/idea)
- Claim · Start · Done buttons
📧 Per-branch email-in
- Forwarded jobs land automatically
⚙️ Setup sheet
- Staff, teams, branches — filled once
→
The engine
n8n
Routes everything, runs the schedules, keeps it in sync. Built & maintained for you.
→
Stored & connected
🗄️ Supabase
- Your database — the single source of truth
✅ ClickUp
- Jobs & tasks, synced from the Slack buttons
→
What you see
🏆 Jobs won this week → #wins-revenue
Phase 2 · later
💰 Xero — revenue per job, margins & costings. Bolts onto the same data store once the time's right — no rebuild.
Phasing
Phase 1 — now
The operational tool
- Slack check-ins, job capture & status buttons
- Daily team summary + Jason's 6am view
- Jobs-won board, auto-posted to #wins-revenue
- Your own data store, set up and populated
- Christchurch + Group first, then Wellington + Hamilton
Phase 2 — later
The financial layer
- Revenue per job, margins & costings
- Custom dashboards on top of the data store
- Added as an upgrade once it's the right time
- Built so it bolts on cleanly — no rework
The process
Connect
You approve a small Slack app and confirm access. One-off.
Build
We build the flows and your data store on our side.
Test
We test it together with a couple of users.
Go live
Switch on for Christchurch + Group.
Roll out
Extend to Wellington + Hamilton.
Maintain
We keep it running and tweak as you go.