Five capabilities. One record underneath all of them.

A board that answers “what needs me right now” in one look.

The owner opens this between calls, in a truck cab, at 11pm. So it leads with one commanding figure you choose, a row of live readouts, and a queue of the things actually waiting on a decision — not one card per feature.

Your arrangement

Pick the headline figure and order the panels. The board is yours or the shop's default, and the page says which one you're looking at.

Leads and customers, apart

Two surfaces, because a queue and a directory answer different questions. A number that rang in isn't a customer yet.

Your job statuses

Name them, colour them, order them. The shop's own words, mapped onto the phases the product needs.

Price book

Services and job templates. One click builds the job and a draft estimate off it.

Reports

Revenue, collections, AR aging, and who owes you what.

Built for 11pm

Command palette over the whole portal, and a dark mode that was designed rather than inverted.

Every text, call, and review request on your own number.

The Podium half of the stack, riding on the same customer records as everything else — so a thread sits beside that customer's jobs, invoices, and payment history instead of in a separate tool that has never heard of them.

Texting

Two-way, with photos, delivery receipts, and STOP/consent handled for you.

Calls

A softphone with real hold, call waiting, recording consent, and business-hours routing.

Missed calls

Text back automatically and open as a lead, before anyone has looked at a screen.

Shared inbox

Run it as one pile the whole shop works, or assign threads per person.

Team chat

Internal DMs and group chat in the same inbox as the customer threads.

Templates

A message library, saved drafts, and an automations page you control.

Review asks

Timed after the job, reminded once, then stopped — and attributed back to the job that earned the review.

Reading and replying to Google reviews inside Crewbound is written and dormant, waiting on Google API access. Sending review requests and measuring what they convert works today.

Hours that already know which job earned them.

A time clock that isn't tied to jobs just produces a number somebody has to explain. Here every entry carries the job it was worked on, so a timesheet is auditable straight back to the work.

Per worker

Clock mode and pay rate, both set by the office rather than chosen in the truck.

Rate history

Dated, so a raise this month doesn't silently rewrite what last month cost.

Pay periods

Approve and lock one, and see who is on the clock right now.

Roles

Owner, office, and tech, with permission floors that hold.

Worker records

Each with their own timesheet, jobs, and history.

Pushing approved hours into QuickBooks Payroll is the next major piece and is not built. Timesheets are complete and exportable in the meantime.