Skip to content
Sample project

Summit Field Services

Dispatchers assign jobs in one place and techs see their day on their phone.

Dispatch software MVP

Sample project: Summit Field Services is a fictional business. Every artifact on this page is produced by the same tools and templates we use on client projects. 360° photos are public domain samples (credited). Client work appears only with permission.

The situation

Summit Field Services sends technicians out on service calls every day. Dispatch runs on a whiteboard and group texts, so dispatchers cannot see who is free and techs miss job changes sent by text. Invoicing happens separately in QuickBooks.

Scope

What we would build

The scope we would write for this business, in plain words.

  1. Dispatcher boardCreate a job, assign a tech and a time window, and get a warning before two jobs overlap.
  2. Tech job list on the phoneToday's jobs, status updates for en route, on site and done, plus notes and photos.
  3. Automatic arrival textsWhen a tech marks en route, the customer gets a text with the arrival window. The text provider is the one integration, named in the written scope.
  4. Accounts and rolesDispatcher, technician and ops director each sign in and land on their own view.
  5. Admin and day reviewSee and correct every job, and review the day by status and by person.

Engines used

  • Prototype StudioBuilds the website or app prototype from a starter kit and a design direction.
  • Build ReceiptMaps what was built onto one package by readable rules, with its estimate range.
  • Document engineGenerates the written scope, briefs and checklists a project runs on.
The artifacts

Made by our tools, not mocked up by hand

Each piece below is the real output of the engine named on it, computed from this study's inputs when the page was built. Run the same tool on your own business and you get the same kind of result.

Engine Prototype Studio

App prototype

Desktop: Dispatch board

App prototype for Summit Field Services, Dispatch board screen at desktop width. The dispatch board and the technician's phone view from our dispatch app kit in the Dispatch direction. Two edits in the editor: a Sign in screen, because every user has an account, and the sample money cards hidden, because the first version tracks jobs, not invoices. Jobs and names are sample data.

Phone: Technician (mobile)

App prototype for Summit Field Services, Technician (mobile) screen at phone width. The dispatch board and the technician's phone view from our dispatch app kit in the Dispatch direction. Two edits in the editor: a Sign in screen, because every user has an account, and the sample money cards hidden, because the first version tracks jobs, not invoices. Jobs and names are sample data.

Sample The dispatch board and the technician's phone view from our dispatch app kit in the Dispatch direction. Two edits in the editor: a Sign in screen, because every user has an account, and the sample money cards hidden, because the first version tracks jobs, not invoices. Jobs and names are sample data.

Build one like it

Timeline

Timeline and estimate

The Build Receipt reads the prototype above and maps it to one package by rules anyone can check.

Typical timeline

6 to 8 weeks

Once content and access are in. Dates go in the written scope.

How it runs

  1. Kickoff and the signed scope
  2. Requirements and design approved
  3. Build in staging, with your review
  4. Launch checks, your approval, then handoff

Estimate for this build

Functional MVP$2,500 to $6,000 estimate

Sign in makes it a Functional MVP: accounts, saved data and the core workflow.

  • 5 screens: Sign in, Dispatch board, Schedule and 2 moreDesigned, built and handed over with documentationIn the estimate
  • Sign inUser accounts and loginsIn the estimate
  • Records, lists and boardsA real database behind every listIn the estimate
  • CalendarScheduling inside the product; calendar sync is quotedIn the estimate
  • Connections to other toolsBooking, CRM, SMS or payment integrations are quoted by nameQuoted
Payments
50% at signed scope, then 25% at approved prd and drd, then 25% at client launch approval
Typical timeline
6 to 8 weeks once your content and access are in

Lower: Start without sign in and it is Validation Build, $1,500 to $3,500 estimate.

More: Grow it to seven screens and it becomes Launch-Ready MVP, $3,750 to $9,000 estimate.

Not in the estimate
  • Domain, hosting, email, payment processing, premium plugins, third-party APIs, stock assets, and paid advertising costs
  • New screens or workflows after approval (change requests)

Estimate ranges from our packages. Your written scope sets the exact price, within or near this range, after a short call. Nothing is billed until you accept it.

Documents

What you would get in writing

Every project runs on written documents you approve. This is the set for this package.

  • Statement of WorkThe fixed price, deliverables, milestones and payment percentages you sign.
  • Product RequirementsUsers, flows, requirements and the acceptance checks for each one.
  • Design RequirementsScreens, states, responsive behavior and accessibility rules.
  • Launch ChecklistEvery check that has to pass before anything goes live.
  • CloseoutWhat shipped, who owns which account, and what comes next.

The full generated set for this sample: Product Requirements, Design Requirements, Technical and Data Brief, Scope Brief, Statement of Work, Kickoff Brief, Launch Checklist, Build Pack and Closeout.

Read the sample documents

Next step

Your business next

Tell us what you need and a person at Cornerstone replies with a clear next step. Or run the same tools on your own business first, free.

Start a project like this Functional MVP, $2,500 to $6,000 estimate

Run this tool on your business