Skip to main content
The ForgeThe Forgeby HustleForge

The Forge’s platform architecture, in full

This is the reference version of /platform: every record type The Forge tracks, how information connects across departments, how automation stays inside the limits you set, how every dashboard number traces to its source, how industry blueprints configure the same core platform, and how work moves through a full lifecycle.

What information does The Forge keep track of?

22 types of information, grouped into six categories below. Each one is tracked on its own — not just a field bolted onto a customer record.

People & Relationships

Every person and business you work with — customers, vendors, and your own team.

CustomersContactsVendorsEmployeesContractors

Commercial Records

What was sold, agreed to, delivered, and billed — the paper trail behind revenue.

Products / SKUsOrdersContractsInvoices

Work Records

The work itself — where it happens, what it involves, and what it needs to get done.

ProjectsWork OrdersWork ItemsAssetsLocations

Communication & Growth

Every conversation and every marketing effort, linked to the customer it's about.

CommunicationsCampaigns

Risk & Governance

What could go wrong, what did go wrong, what controls exist, and who signed off.

RisksIncidentsControlsApprovals

Reporting & Automation

Reports and automated actions that respond to what's happening in the other five groups.

MetricsAutomations

One shared record — not five copies of the same customer.

Every piece of information The Forge tracks connects directly to the records it naturally relates to. A department doesn't get its own separate database — it gets a view into the same information, scoped to what its role needs.

Worked example

Follow one Customer record across every department

  • CommercialOrder / Contract / InvoiceWhat was sold, agreed to, and billed — visible without leaving the customer record.
  • OperationsProject / Work Order / Work ItemWhat work is scheduled, in progress, or completed for this customer.
  • GrowthCommunications / CampaignEvery message across every channel, and which campaign originated the relationship.
  • Risk & GovernanceIncident / ApprovalAny open issue tied to this customer, and who approved the actions taken.
  • IntelligenceMetric / AutomationLifetime value, margin, and which automations are configured to act on this record.

Sales sees the pipeline. Operations sees the work order. Finance sees the invoice. All three are looking at the same customer record — updated once, visible everywhere it matters.

You set what needs approval. Automation only runs inside those limits.

Every automation in The Forge runs inside the role, approval, and access limits you set — nothing acts outside them. That discipline is what keeps a fast-moving system from breaking trust.

Rules keep automation in check

Role-based limits
Who can approve what, up to what threshold, for which business or location.
Approval requirements
Which automated actions still require a human sign-off before they execute.
Data access
Which records a role, integration, or automation can read or write.
Rate and volume limits
How often an automation can act, to prevent runaway loops.

What runs inside those rules

  • When a new lead arrives from a connected source

    Then deduplicate against existing customers, assign an owner, and send the configured first-touch message.

  • When a work order is marked complete and approved

    Then assemble a billing-ready invoice draft from logged labor and materials.

  • When a vendor invoice fails to match its purchase order

    Then route the mismatch to an exception queue instead of posting it silently.

  • When a metric crosses a configured threshold

    Then notify the metric's owner and optionally open a work item.

  • When an integration's credential is nearing expiration

    Then alert the provider owner before the connection breaks.

Every number explains where it came from.

Every number on a Forge dashboard is built the same way: it always shows the six things below. If you don't trust a number, you can check exactly where it came from instead of asking around.

Formula

The exact calculation behind the number — not a label, the math.

Sources

Which records and connected systems feed the calculation.

Freshness

When the underlying data last updated, so a viewer knows how current the number is.

Data quality

Whether required inputs are complete, and what's missing if they're not.

Owner

The role or person accountable for the metric being correct.

Scope

Which business, location, team, or time range the number covers.

Worked examples

Job Margin %

(Billed amount − actual labor cost − actual material cost) ÷ Billed amount

Sources
Work order labor entries, Material line items, Approved invoice
Freshness
Updates as labor, materials, and billing post to the job record
Scope
Per job, rollable to project, crew, or business

Pipeline Coverage

Open pipeline value ÷ Remaining period revenue target

Sources
Open opportunities, Stage and probability, Configured revenue target
Freshness
Updates as opportunities change stage or value
Scope
Per sales owner, rollable to team or business

The six fields above are the standard we’re building every metric to meet. See what’s live on your account today at Product availability.

One product. Set up differently for each industry — not rebuilt from scratch.

An insurance agency and a home-services company run on the same underlying system. What differs is the setup on top — terminology, default workflows, warning signs, and the systems each industry connects to.

  1. 1

    Core platform

    The same information and work-and-approval process for every customer, every industry.

  2. 2

    Industry blueprint

    Terminology, default workflows, warning signs, and connected tools tuned to the industry.

  3. 3

    Business-specific setup

    Roles, limits, and which modules are turned on, set during onboarding.

Security & Governance

Everything above runs inside access, approval, and audit controls.

Your records, work and approvals, automation, and every connected system all run under role-based access, approval gates on sensitive actions, and a recorded history of activity. That’s a full page on its own — control status, shared responsibility, and industry-specific boundaries all live there.

Read the full security and governance model

Your setup starts on day one — and grows with your business from there.

Every plan includes Guided Launch. The optional Forge Operational Blueprint ($249) adds a professional review of your current systems and workflows before you launch.

Guided Launch

Included with every plan. Work through a structured launch and earn Forge Credits as your team completes each onboarding milestone.

  • Industry template selection
  • Structured setup checklist
  • Native integration connection within your plan allowance
  • Standard import templates for your records
  • Recorded training for your team
  • Validation checklist and go-live readiness review
  • Your team performs the data preparation and connection steps
  • Earn Forge Credits as milestones are approved

Managed Launch

You provide access, context, and approvals. Our team configures, connects, migrates, tests, trains, and launches The Forge remotely.

  • HustleForge performs the configuration and supported integrations
  • We migrate your customers, jobs, staff, and history
  • Your existing systems keep running until you approve the switch
  • Testing, training, and a coordinated go-live — remotely
  • Can be paid upfront, distributed over six months, or included in an Operations annual agreement
  • Your final quote is confirmed during discovery

Forge Credits

Complete approved onboarding milestones and earn credits that reduce eligible launch costs. One Forge Credit equals one dollar toward qualifying setup, training, migration, or integration work.

1 Forge Credit = $1 toward eligible Forge services

Watch how work actually moves through a real business process.

Each journey below follows a process from start to finish, moving through several types of information and people, and is upfront about which steps hand off to a system that keeps its own official record.

Lead captured

A new inbound request creates a job in the pipeline.

Qualified

The job is scoped and quoted before any work is scheduled.

Scheduled

A crew and time slot are assigned once the quote is accepted.

Delivered

The crew completes the work on site.

Invoiced

Completed, approved work becomes an invoice — no re-entry.

Collected

Payment is recorded against the same job record.

Exception surfaced

A missing signature is flagged for follow-up instead of getting lost.
Forge — Pipeline
  • Ferreira Landscaping

    Spring cleanup, 4 crew hours

    $420New
  • Redwood HOA

    Irrigation repair, block C

    $1,150Quoted
  • Community roofing job

    Shingle replacement, 2 units

    $3,600Scheduled
  • Alvarez residence

    Gutter cleaning

    $210In progress
  • Harbor View Apartments

    Quarterly pest control

    $890Invoiced
  • Nguyen family home

    Deck staining

    $540Paid

Go deeper on a specific process

  1. 1
    ProspectSubmits an inquiry through a form, call, referral, or campaign response.
  2. 2
    The ForgeCreates or matches the customer record, deduplicates, and assigns an owner by rule.
  3. 3
    Sales / officeQualifies the opportunity and schedules the next step.
  4. 4
    The ForgeGenerates a quote or proposal from the product/pricing catalog.
  5. 5
    CustomerApproves the quote or requests changes; approval is logged against the record.
  6. 6
    The ForgeConverts the approved quote to a scheduled work order, order, or project.
  7. 7
    WorkforceDelivers the work; time, materials, and status update the same customer record.
  8. 8
    The ForgeAssembles a billing-ready invoice from completed and approved work.
  9. 9
    Accounting systemPosts and collects the invoice.

    The Forge is never the general ledger — it hands off a reconciled, billing-ready record.

  10. 10
    The ForgeRequests feedback and logs satisfaction against the customer's history.
  11. 11
    The ForgeSurfaces the account for renewal, reactivation, or expansion based on configured signals.
  12. 12
    Owner / managerReviews the account's full lifecycle value before the renewal conversation.
Build your Forge plan
  • One connected view of customers, work, and money
  • Keep the tools that work, replace the ones creating duplicate work
  • Each employee sees only what their role needs
  • Dashboards you can trace back to the source record