Sample Forge Plan

This is a fictional example, not a real customer

"Example Co." below is invented for this page — a fictional 12-person home-services company (HVAC repair and install), not a real business, testimonial, or case study. Nothing on this page describes an actual customer, outcome, or result. It exists to show the shape of what a Blueprint conversation produces: a systems map, a proposed configuration, and a launch recommendation, built from real Forge Core plan features and real launch-path options. Your own Forge Plan is built from your onboarding answers, not from this template.

Example Co. — current-systems map (before The Forge)

What a 12-person HVAC repair-and-install business might be running today, as captured during a Blueprint software inventory.

• Spreadsheet — job scheduling and technician assignment, updated by hand
• A separate quoting tool — estimates typed in a second time after the spreadsheet
• A basic accounting package — invoices re-entered manually once a job closes
• A shared inbox — customer requests triaged by whoever checks it
• Paper timesheets — collected weekly and re-typed for payroll

Proposed workflow configuration (illustrative)

Based on Example Co.'s size and current-systems map, a Blueprint would typically recommend Forge Core configured around these workflows.

• One intake form replaces the shared inbox — every request becomes a lead with an owner
• Quotes and estimates built and sent from the same record as the lead — no second typing pass
• Jobs scheduled and assigned to technicians from one calendar view
• Basic financial dashboard replacing the manual invoice re-entry step
• Employee records and time visibility replacing the paper timesheets
• Ten automated workflows and three native integrations

Integrations to connect (illustrative)

Which of Example Co.'s current systems would be connected rather than replaced — confirmed during the Blueprint, not assumed here.

• Accounting package — connected as a configurable API integration; it stays the official ledger
• Payroll (once added) — would stay the official payroll processor and tax filer if Example Co. adds one
• See the full status vocabulary in the integration guide for what each connection type means

Role and permission setup (illustrative)

• Owner — full access, financial dashboards, approval authority
• Office manager — customer and job management, quoting, scheduling
• Technicians — view and update their own assigned jobs, log time, no financial visibility
• Unlimited view-only users — for anyone who just needs to see status, at no extra seats

Recommended launch path (illustrative)

For a 12-person team without dedicated IT staff, a Blueprint would typically recommend Managed Launch over Guided Launch — trading the guided launch team-hours cost for a remotely configured, migrated, and tested launch. Guided Launch included, or Managed Launch at $1,250.

Illustrative timeline

A single-location Managed Launch on this plan typically runs the same five-week timeline covered on the Launch page — Blueprint confirmation, configuration, integration connections and migration, testing and training, then go-live.