download dots

🎛️ Build a Service Operations Command Centre

Use answer-first prompts to design data models, approval matrices, executive reviews, portfolio risk systems, job costing, cash scenarios, vendor SLAs, commission trackers, retention dashboards, and customer health scorecards. Each prompt asks for the operating rules and evidence needed before generating an app or workflow.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Build a Service Operations Command Centre

Copy

I run a service business from a diary, a spreadsheet and my phone. Build me an operations command centre. Keep customers with their sites, contacts and history. Keep jobs with the customer, the site, the work required, the priority, the scheduled date and window, the assigned crew, the status and any parts needed. Keep crews with their members, skills and working hours. Give me a dispatch board showing today, tomorrow and the week, with unassigned jobs shown prominently since that is what costs money. When a job is completed, the crew records what was done, the time taken, parts used and photographs, from their phone, and that flows into an invoice. Give customers a portal where they sign in and see their own jobs, status, history and documents, set up so one customer can never see another, and let me test that with a second account. Add an AI agent I can ask what is unassigned tomorrow, which jobs are at risk of missing their window, and which customers have had repeat visits for the same problem. Automate three things: notify the customer when a crew is on the way, chase any job completed but not invoiced, and a scheduled daily morning summary. Three logins: a crew member who sees their own jobs, an office user who dispatches, and an owner who sees everything.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Build a Service Operations Command Centre

Run customers, jobs, crews, and invoices from one dispatch board with a customer portal and an operations assistant.

// the spark catches · intelligence awakens · the answer unfolds

Service businesses run on four things: who the customer is, what the job is, who is doing it, and whether it has been paid. This puts all four in one place with a customer portal on the front.

What's Included

  • Customers, jobs, crews, and invoices linked rather than in four systems.
  • A dispatch board showing today, tomorrow, and what is unassigned.
  • A customer portal for job status and history.
  • An assistant that answers questions about the operation.

How To Use

  1. Link jobs to customers, crews, and invoices from the start. Retrofitting is painful.
  2. Put the unassigned work in front of you. That is the thing that costs money.
  3. Give customers a portal and test it with a second account.
  4. Add your own domain on Business plans and above, at $25 per month billed annually.

Cost the jobs with job time costing, and quote them with quote prompts.