Product availability, capability by capability

Admissions applications

Track each family's application — applicant, guardian contact, and three independently-set dates: the application deadline, the deposit due date, and the enrollment confirmation window — and bind a scheduled workflow to any of the three so a reminder fires the number of days before it you choose. The Forge is not a school information system or admissions CRM: it holds no test scores, transcripts, financial-aid detail, or document checklists.

Two-person approval for retainage and invoice payment voids

A retainage release or an invoice payment void can be requested by a billing user and is applied only after a different Owner, General Manager or Finance user approves it. The requester cannot approve their own request, a request nobody decides within seven days expires without applying, and every request, decision and applied change is recorded in the audit log. The Owner can turn on a setting that makes these two actions go only through that request, and off again, and each change is recorded. Invoice payment voids and construction draws show the request and the pending approvals.

Billing & plan entitlements

Every plan tier's own subscription, usage, and unlocked capabilities are visible from one place. Where the platform's payment processor is configured, an Owner upgrades through hosted Checkout; where it is not, plan changes are handled directly with the account team.

Blueprint engine

Structured Blueprint intake that generates a customer-specific Forge Plan grounded in platform capability status.

Industry blueprint library

Every shipped industry blueprint — operating areas, recommended workflows, connectors, roles, and a launch outline — is browsable inside your own workspace, cross-linked to the real starter pack where one exists for that industry.

Bulk customer & lead import

A JSON or CSV batch of customers and active real-estate leads can be imported directly into a migration job, with a row-by-row imported/updated/matched/failed report. Customers converge onto the same Customers list a phone call, web form, or social inquiry would produce, rather than ever creating a duplicate or landing somewhere the Customers screen doesn't show.

Customer outcome report (Owner and General Manager)

Owners and General Managers see six outcome figures from their own records for a chosen period: response time to new leads, lead conversion, estimate follow-up coverage, days from job completion to invoice, on-time job completion, and collected revenue. Each figure shows its sample size and shows not enough data instead of a number when the sample is too small.

Callback tracking

Callback hours are recorded as their own labor category, and each job shows its callback hours and cost as rework by crew member. Reporting callbacks as completed versus first-visit completions, by job type, is not available yet. Planned.

Certified-payroll report draft by project and week

A certified-payroll report draft for review, by project and week. For each worker it lists classification, daily and weekly straight and overtime hours from your own time entries, and the rate paid compared with the prevailing rate you entered for that classification and locality. Rows are flagged when the rate paid is below the required rate, or when a classification or wage rate is missing. Hours that are not yet approved are flagged, and each correction to an entry is shown with its audited before and after values. Export as CSV, or as a printable page, in WH-347 column order: name, last four digits of the SSN, work classification, hours for each day, total hours, rate, and gross pay. Deductions and net are left blank for your payroll administrator. It is a draft for your review: not a certified payroll report or a WH-347 form, not checked against any agency's rules, and not accepted by any agency.

Owner and architect acknowledgment of change orders

A sent change order can be routed to its owner or architect for acknowledgment. The office copies a one-time link, or emails it to the owner or architect from the same screen (an email goes out only when someone clicks Send by email); it opens on a page that shows only that change order, and the owner or architect can acknowledge or decline it once. An acknowledged change order is billed through the change-order automation, and a declined one is never billed. Links expire after 14 days and can be revoked.

Commission forecasting & approval visibility

A commission can be forecast, approved by a different Owner or General Manager than whoever forecast it, and reconciled against what was actually received - a visibility and approval layer only, never a replacement for your accounting system's own books.

Customer commitments

Record each promise the business makes to a customer: what was promised, who owns it, when it is due, and the job, estimate, invoice or message it relates to. Each commitment is marked kept, missed or cancelled once, and every change is kept in its history. Commitments that pass their due time without a close escalate in the app to an Owner or General Manager. Nothing is sent to the customer.

One communication timeline per customer

Texts, emails and calls the platform itself sends or receives for a customer, plus booking confirmations, show in one newest-first timeline on that customer's record. A call or text appears there when the number on it matches that customer's phone number. Texts and calls from numbers that match no customer are kept in an Unmatched conversations queue on the Customers page. Someone with customer access can link them to an existing customer, create a new lead from the number, or dismiss them as spam; nothing is created until they choose. Nothing is read from your own phone or mailbox provider, and automatic missed-call replies are not on the customer timeline yet.

Consolidated financial statements

Businesses running more than one native-ledger legal entity get a consolidated trial balance, profit and loss, and balance sheet — each entity's statement is still computed independently, tagged with which entity it came from, and only summed at the moment you view it; nothing is ever merged in storage. Entities kept on an external accounting connector are listed as excluded, never guessed at. Intercompany transactions between two of your own entities can be manually marked as a linked pair so both sides are excluded from the consolidated totals and shown separately, rather than double-counted or silently dropped; this is manual marking, not automatic elimination.

Consolidated and per-property draft invoices

Bill one customer's completed jobs across their properties on one draft invoice that names each job and property, or on one draft per property. Each job goes on one invoice only, nothing is sent automatically, and cancelling an invoice frees its jobs.

Construction bid intelligence (Level 1: trustworthy bid history)

Every bid keeps its own history: which estimate it was priced from, the reviewed risk register and economic policy behind its floor, what was actually submitted and by whom, and what happened afterwards with a structured reason - so a contractor can look back at real outcomes instead of guesses. The Forge never invents a competitor's price or a win probability, and bid strategy (cost lines, risk register, margin, floor, market evidence) is visible only to Owner, General Manager and Finance roles, never to sales or field roles. Open bids are listed by stage with their value, and win rate can be broken down by estimator, client or project type once there is enough reviewed history. A submitted bid can carry a follow-up that queues one message after a set delay if it has no decision; that message is queued only and is never represented as delivered. An awarded bid opens its contract with the schedule of values and subcontractor plan supplied at award, and a bid converts to one project only.

Construction (T2 vertical) lane

A project's schedule of values, subcontractor compliance documents, change orders, and draw/retainage math live in one workspace: a change order only affects a project's billed total once it is acknowledged, and a draw's retainage is computed from the project's own retainage rate and frozen on that draw. Each required compliance document shows whether it is expired or falls within 30, 60 or 90 days, and a workflow alert fires once as a document enters each window. Contractor licence and bond records carry a jurisdiction and expiry date on the business record, with expiry alerts through a schedule workflow. A submitted, approved or paid draw can be exported for Owner, General Manager or Finance as a G702/G703-style application: an application summary and a schedule-of-values continuation sheet, as CSV or printable HTML. Its figures come from the draw record and the project schedule of values, and a change order counts only once acknowledged. The export uses the common column order; it does not reproduce the AIA form or send anything to a pay-application system. The Forge does not perform estimating, takeoff, or independently certify licensing, insurance, or safety compliance, and does not verify a licence or bond with any authority, which stay the contractor's own responsibility.

Construction plans, takeoffs, assemblies and cost plans

Plan sets and their revisions, manual takeoffs with review, assembly templates, material lists and per-project cost plans are kept in the project workspace for the owning business only; the Forge does not measure quantities from drawings automatically and does not replace estimating software.

Construction procurement action rules

Construction procurement has defined role rules: who may request quotes, select a supplier, issue a purchase order, post a receipt and match an invoice. Supplier prices and unit costs are visible only to Owner, General Manager and Finance roles, never to sales or field roles. The Forge does not yet publish a supplier comparison.

Live website chat

Website visitors can start a chat that lands in your inbox; replies refresh every few seconds. An embed snippet goes on your own site; you can restrict which sites it will run on and turn it off at any time.

Forge Credit earning opportunities

An earning activity can be claimed with evidence, verified by a different person than the claimer, and awarded - the award always posts through the same ledger and per-transaction ceiling as every other credit award, never a side channel.

Crew double-booking refused at job assignment

A crew member cannot be assigned to two open jobs whose scheduled windows overlap, and a subcontractor cannot be booked onto two overlapping windows. The assignment is refused and names the conflicting job or project, and nothing is written.

Crew performance and expedited crew recommendation

Efficiency is measured per job against the typical labor hours for that service line, so job mix does not favour anyone. Managers see each person's efficiency index and each crew's average labor per job, once a person or crew has at least five scored jobs in the last 90 days; before that it reads 'not enough jobs yet'. Callback rework is reported separately and does not count toward speed. Emergency and urgent jobs get the fastest qualified crew instead. Employees see only their own row.

Crew balancing suggestions and apply

Efficiency is measured per job against the typical labor hours for that service line, so job mix does not favour anyone. Managers see each person's efficiency index and each crew's average labor per job, once a person or crew has at least five scored jobs in the last 90 days; before that it reads 'not enough jobs yet'. Callback rework is reported separately and does not count toward speed. Balancing suggests single swaps between crews on booked jobs that narrow the gap between crew averages, skipping any swap that breaks a credential, service area, company assignment or existing booking. Each suggestion shows the crew averages before and after. Nothing moves until a manager applies it, and every applied move is audit-logged. Emergency and urgent jobs are never balanced. Pro plan.

Crew utilization and per-person trends

For each crew member, managers see billable hours against published shift hours for each of the last 12 complete weeks, in your timezone. Hours are split into approved and unapproved, and each person's callback rate, jobs worked, revenue per billable hour, close rate and median lead response time are shown by week. A week with no data reads 'not enough data', not zero. Employees see only their own trend. Moving hours between crew members from these figures is not built.

Cross-business staff allocation

Staff who work across your businesses appear on one read-only list, and each booking and time entry is labelled with the business it belongs to. Time goes to the business of the job, not the worker's home business, and labor cost by business adds up to each worker's total. A worker cannot be double-booked across businesses, and you only see the businesses your access covers. Moving approved time to another business needs a reason and leaves a record. This is wage-summary visibility; The Forge does not run payroll. Limited release.

Cross-business sharing of staff, workflows and templates

Share a staff member, a workflow or a content template from one of your businesses with another business in your account. A shared staff member can be assigned to work in that other business, while their pay and HR records stay with their home business and are never shown there. A shared workflow or template is copied into the other business as a draft when you choose to copy it; the copy is never switched on by itself. Revoking a share stops new copies and new assignments and leaves everything already made in place. Only an Owner, or someone who manages both businesses, can share, and nothing is ever shared with another account. Syncing later changes from the original into existing copies is not part of this yet.

Customer churn-risk flags from explicit rules

Flags customers whose own records break a rule you can read: no job activity for a set number of days, repeated skipped visits, an invoice past due with a balance still open, an old open complaint, or an active agreement nearing renewal. Each flag names the rule and the records behind it, clears itself once the rule stops holding, and the Owner sets the thresholds. These are plain rules, not a prediction score, and nothing is sent to the customer.

Customer equipment & service history

Record the equipment installed at each customer's site, with its warranty details, and see every job that has serviced it.

Customer portal (magic-link, self-serve)

Your own customers get a login-free, emailed link to their own portal — where they can see every estimate and invoice from you, accept or decline a quote, pay a bill, and check a job's schedule status — scoped to exactly their own records and nothing else. Included on every plan, not gated to a higher tier, because it makes every other native tool (jobs, estimates, invoicing) more useful the moment your business turns it on.

Data subject rights requests (CCPA/CPRA)

An outside individual — one of your customers or employees — can submit a CCPA/CPRA rights request (know, access, delete, or correct) through a public form, verify it by email, and have it routed straight to your business's Owner. The Owner reviews the request, fulfills it by export or delete, or refuses it with a recorded reason, inside a 45-day statutory clock with one permitted extension. A request naming no business The Forge recognizes, or about a Forge account itself, is fulfilled by Forge's own operators instead.

Customer delay notices for weather days

When a weather day is logged, each flagged job gets one customer delay notice, queued in the communications log. A notice is sent only when the business Owner has switched on customer delay notices (off by default; the switch is in the weather delay panel) and the customer has granted email consent; otherwise it stays queued, or is kept as a draft with the reason shown. A dispatcher sends a queued notice from the weather delay panel. A failed send can be retried, and a sent notice is never sent again. The owner edits the notice wording. No messaging provider is connected by default, so notices stay queued until one is.

Brand colors

Set one brand color and a corner style, and the platform works out a matching set of colors from it — button and heading color, page background, text ink, and divider lines. Every text-on-background pair is checked against the WCAG AA contrast standard (4.5:1) and adjusted automatically if it falls short, so nothing it produces is unreadable. Available through the API at this stage: your generated documents, emails, and share cards do not read from it yet, and setting it changes nothing about how they look today. Your logo stays managed under Branding.

Dispatch board: overdue visits and open crew slots

The dispatch board lists recurring visits that are past their due date and still not completed, with the days overdue. It shows each crew member's open minutes for a day: published shift time minus booked job time. It can be narrowed to one service area. Viewing the board books nothing; a slot that was taken in the meantime is refused when you assign the job. Route ordering and customer delay notices are not part of it. Limited release.

Document upload & review queue

Upload receipts, invoices, and statements to a review queue, then match them to a transaction yourself or create one from the document with a few manual fields. The platform will highlight an amount, date, or vendor it noticed in the filename as a starting hint. When extracted text is available for a document (via a connected OCR/read service), the platform can additionally match it against a vendor invoice template — your own saved templates or a built-in starter set for common vendor formats — to fill in more hints (invoice number, total, date, tax, and more), each shown with the exact text it was read from. These remain hints only: nothing here ever creates or matches a transaction automatically, and template matching never runs without extracted text already existing.

Branded PDF documents

a branded PDF of any estimate or invoice, generated in-house from the same record that the web page shows, with a JPEG logo if you have one set, or your business name in your accent color if not, available to you and to the customer from their existing link; no third-party service sees the document

Donations

Record a gift with the donor's name, email, phone, amount, date, method, and fund. A donor email is matched, case-insensitively, against your existing customer records automatically — a gift does not have to be hand-matched to a person before it can be logged, and one that cannot be matched stays visibly unmatched rather than silently creating a new customer. Bind a scheduled workflow to donation.recorded so an acknowledgment is queued the moment a gift is entered, and to a gift's received date (with an offset, e.g. 365 days) for a stewardship-milestone reminder. The Forge is not a fund-accounting or donor-management system: this release holds no pledge object, no fund-level reconciliation, and no tax-receipt PDF, and it does not itself transmit the acknowledgment — a person confirms it went out.

Draw check against field progress

Draw requests are checked against the field progress logged for each schedule-of-values line, from the moment a draft is saved. A claimed percent complete above the latest logged value, beyond the tolerance the business sets, flags the draw for review before it is submitted. A flagged draw can be submitted only with a reason recorded by an Owner or General Manager. The check never changes a draw's amount or retainage. Superintendents can attach field photos to a progress entry as evidence.

Email marketing campaigns

Build a real audience from your own customers and prospects, honestly excluding anyone who has revoked consent or been suppressed, then send and track an email campaign through this platform — every send re-checks consent immediately beforehand, and every message carries a working one-click unsubscribe that stops future sends for that person everywhere, not just in this campaign. Available on Pro and Operations plans, up to your plan's active-campaign limit.

Emergency triage queue and displaced-job rescheduling

Emergency jobs wait in a triage queue. Crews are ranked by how few booked jobs an emergency would displace, with ineligible crews listed and the reason shown. Accepting an emergency flags each displaced job for rescheduling and creates a call-the-customer task for each one, all in one write. Cancelling the displacement reverses both. No message is sent to the customer automatically.

Company equipment allocated to jobs

Company trucks, trailers and tools can be allocated to a job for a time window. A piece of equipment cannot be booked to two overlapping jobs. Equipment can be marked out of service with a reason: it cannot be allocated while out of service, and a booking already on it is flagged for dispatch rather than cancelled. and its cost comes from an hourly or daily rate recorded when it was allocated, counted once in the job's economics.

Estimate aging and stale-estimate handling

On the Estimates list, every open estimate shows its age, how long it has sat idle, its follow-up state and next follow-up date, and the total value waiting; the list can be filtered to estimates past their follow-up window or past a maximum age. An Owner can set a maximum age for open estimates: past it, the office gets a stale-estimate task, once per stall. Automatic closing of stale estimates is off unless the Owner turns it on, and a customer acceptance always wins. No email or text is sent by this feature.

Email an estimate to the customer

A staff member with estimate access can email an estimate to the customer from the estimate screen. The email has a default message the Owner can edit, and it carries the customer's view-and-respond link. The customer's email consent and opt-out are checked before anything is sent, and the email appears on the customer's timeline. If no email provider is connected, the Forge says the estimate was not sent and keeps the email queued. Nothing is sent automatically; each email is sent by a person pressing Send.

Estimate follow-up policy

An Owner can turn on an automatic follow-up for estimates that go quiet — set the delay, the channel, and the message — and a scheduled run queues that follow-up once an estimate has sat unanswered that long. This queues the message only; it does not itself call an email or SMS provider, and is never represented as delivered.

Estimate follow-up coverage report

An Owner can add a call task to the estimate follow-up: when an estimate has gone unanswered for the delay they set, one open call task is created for the salesperson who wrote it, once per due date. A call task that stays open past its due time by the escalation window is escalated to the owner and general manager once, and a finished one never is. An Owner can also see a follow-up coverage report on the Estimates page for any period in their business's time zone: how many estimate follow-ups came due, how many were acted on, how many were completed on time, late, or are still open, and the value of estimates that converted after a follow-up, by person and by lead source; and, for new leads, how many were contacted within 24 hours. Every rate sits beside the counts behind it. Nothing is sent by a call task, and a queued message is never counted as completed. Jobs are not in the report.

Estimate customer view history

The Forge records when a customer opens an estimate's share link: first and last view and how many times, with staff and bots not counted. The estimate shows that history, and the open-estimate list flags estimates the customer has viewed but not accepted. When an estimate is emailed from the Forge, the email can include a small image that reports when it was opened, and the email says so. Opens are estimated, and some email apps load images automatically, so an open can be missed or reported when nobody read the email.

Estimate decline reasons and win/loss by salesperson

Declining an estimate asks why, from a fixed list (price, a competitor, timing, scope, no decision, or other) with an optional note, whether the office records the decline or the customer does through their link or portal. Owners and general managers see won, lost and open estimates by salesperson, lead source and service line for any period in the business's own timezone, with the value of each, the win rate with the number of decided estimates behind it (no rate is shown until there are at least five), the average days to decide where the decision time is recorded, and why estimates were declined. Salespeople see their own estimates only. Drafts are not counted.

Field supply usage logging

Field staff log the supplies they use against a job in whatever way is fastest to say — an exact amount, a fraction of a container, or one tap for finished the bottle — and can fix a mistake afterward without the original entry disappearing. Each entry updates your item's usage history automatically, feeding the same trailing-usage reorder suggestions your office already sees, with no extra data entry required from anyone. Field staff see and correct only their own entries; cost, current stock, reorder points, and supplier details are never shown to them. If a staff login isn't linked to a staff record yet, logging says so plainly instead of silently failing.

Fleet vehicles and meter readings

Vehicles are tracked as assets with make, model, VIN, plate and cost fields, and odometer or engine-hour readings are recorded as an append-only history: a reading below the current one is refused unless it is explicitly marked a correction with a reason, and the reason is kept in the audit trail.

Fleet GPS tracking and weather-forecast connections

An Owner can connect a GPS fleet provider and a weather-forecast provider with their own API keys, and disconnect either one. With no GPS provider connected, the vehicle view says live tracking is not connected and shows no position. Each vehicle is linked to its provider vehicle, and the latest reported position is shown with its time. A late-arriving location is kept in history but never moves a vehicle back in time, and a re-delivered provider event is stored once. Forecast days show the chance of precipitation and the temperature range by the business's local day. Both connections are in limited release: the adapters are built and tested against recorded payloads, and a live provider account must be connected before any live data appears.

Forge Plan generation & approval

Once a Blueprint intake is submitted, a customer-specific Forge Plan is assembled deterministically from that intake and platform capability status, then approved by an account Owner — no model or AI call drafts the plan itself.

Per-unit P&L with cross-unit roll-up

Revenue, labor cost, direct job cost and the operating expenses recorded for each unit, with a roll-up across all units and a profit after operating cost for each unit that has recorded expenses. A unit with no recorded expenses says to add expenses by location rather than showing a profit after operating cost. Expenses are recorded by unit from the same page. The page refreshes every 30 seconds while it is open.

Send payroll hours to Gusto from Forge

Finish payroll hours in Forge and send them to Gusto. Match your employees and jobs to Gusto once, review the exact hours for each employee and job, and confirm. Forge writes them into your unprocessed Gusto payroll for that pay period. Sending the same export again replaces the hours rather than adding them. Gusto still runs the payroll; the Forge does not calculate taxes or move money. Hours that belong to a period Gusto has already processed are listed as exact steps to enter in Gusto, and you mark each one done. Owner and Finance only. Every send is recorded in the audit log.

Public help center

A public help page for your customers with the articles you write and a search box that works entirely in the visitor's browser. Nothing is generated by AI; every word is what you typed.

Inbound email

A dedicated inbound email address per workspace. Received mail is recorded as a communication with its attachments, matched to a lead or customer by sender address when possible, and the Owner and General Manager are notified. Nothing here sends or auto-replies to anything.

Lease-term inspections

Schedule move-in, periodic, move-out, and maintenance inspections against a lease, and bind a scheduled workflow to the scheduled date so a reminder fires the number of days before it you choose. Every inspection stays linked to the lease it belongs to, so a lease's full inspection history — and its owner statement for any period — always includes them.

Insurance claims on jobs

Record a customer's insurance claim against a job: the carrier, claim number, adjuster, deductible, the amount the carrier approved and the amount it has paid. Supplement scope requested from the carrier is tracked with the amount requested and the amount approved. Each approval or reduction is raised as a draft change order on the job, and a duplicate claim number for the same carrier is refused. The Forge does not contact the carrier, and nothing is sent or charged from a claim record.

Insurance policy renewals

Track each policy you manage — carrier, policy number, and its expiration date — and bind a scheduled workflow to that expiration so a renewal reminder fires the number of days before it you choose, commonly 90. The Forge is not an agency management system: it holds no premium, coverage-limit, commission, or claims detail, and does not bind or service coverage.

Partial invoice payments and balances

Records partial payments against an invoice: each payment posts to the invoice's payment history, the remaining balance shows, and a payment can be voided. Overpayments are refused.

Pay now on an invoice (flagged checkout)

When pay-now is turned on for a business, a native invoice's open balance can be paid through a hosted checkout on that business's own connected processor, and the payment is recorded against the invoice once the processor confirms it, once only however many times the confirmation is delivered. On by default; the business can switch pay-now off. It needs a connected processor.

Automatic draft invoice on job completion

When an owner turns it on, completing a job creates a draft invoice from the job's price or its accepted estimate. Nothing is sent automatically, and each job gets at most one invoice, even when it is reopened and completed again.

Change orders on native jobs

A change order can be raised against a job directly, without a construction project: it carries priced lines, is acknowledged by staff, and its approved amount is invoiced exactly once. An employee assigned to a job can request a change order from the job screen: it is saved as a draft with priced lines, a retried submission does not create a second one, and the office reviews it before it goes anywhere. A change order flagged as affecting permitted work raises a warning on acknowledgment when the job has open permits; it never blocks the acknowledgment.

Job budgets by cost code (budget vs actual, variance)

Each job can carry a budget broken down by cost code. Budget versus actual is calculated for each code on every read, with variance, percent used and an over-budget flag, and it shows unassigned cost on its own line. Budget changes are saved as numbered revisions, so earlier budgets are never overwritten.

Job cost roll-ups by service line, client, crew and location

Job revenue, labor, materials, subcontractors, equipment and overhead roll up by service line, client, crew and location, with margin by client and cost per unit where a job defines its units. Each total is the sum of the same per-job figures shown on the job, and jobs with no service line, client, crew or location appear under Unassigned.

Per-job profitability rollup

A job's real revenue, labor (scheduled vs. actual), materials, subcontractors, equipment, and overhead roll up into one per-job profitability figure — computed from records you already have, never estimated.

Job permits & inspections

Track each job's permits and required inspections with their status and dates. A job cannot be marked complete while any of its permits is still open or has failed inspection. Creates a My Work task before a permit expires or an inspection is due: 14 days and 3 days ahead, and once when overdue.

Job stages, next actions and stall alerts

Each stage of a job has a defined next action and, when you set one, an expected time. A job that stays in its stage past that time raises a high-priority task and an in-app notification for the Owner, once per job per stage. The Jobs screen shows how many jobs sit in each stage and how long the oldest has been there. Each stage move is recorded, and a move made from an out-of-date view is refused instead of overwriting the newer one.

Live KPI overview with drill-down

The business overview shows job volume, estimate conversion, lead-to-job conversion and automated messages queued. Each figure carries its value, the period in your business's time zone, when it was read, whether it is automated or entered, and a list of the records behind it, so every number can be checked. Figures are computed when you open the overview, not pushed in real time, and a figure with nothing to measure yet says so instead of showing zero. Automated messages are counted as records queued by the platform, not as confirmed deliveries.

Scheduled KPI report delivery (daily, weekly, monthly)

An Owner can schedule a KPI report daily, weekly or monthly. Each run stores one snapshot of the chosen overview figures, with the formula and the time each was read, and tells members in the app. Email is sent by default; your business can switch it off, and the snapshot says when an email was not sent.

KPI threshold alerts

You set limits on job gross margin, job cost used against budget, lead response time, and how long an open quote has been out, for the whole business or one company. When a job, lead or quote crosses its limit, the platform adds an in-app alert for Owners, Finance and General Managers with a link to that record. Each record alerts once per day for each limit, and a record with no figures yet is shown as not enough data rather than alerting. An alert nobody acknowledges escalates once to the General Manager or Owner as a task after the escalation rule window you set. Alerts stay inside the app; nothing is sent to customers.

Labor categories and callback/rework cost

Each time entry is categorized as production, drive, setup, callback or non-billable, and each job shows its labor hours and cost by category. A callback names the prior job it revisits and its cost is shown there as rework, by crew member. Callbacks must fall within 30 days of that job unless an office user records an override.

Daily labor-cost digest with budget variance

Each morning, owners, general managers and finance get an in-app labor-cost digest for each entity covering the previous day: hours and cost for approved and not-yet-approved time, each job against its budget, the most over-budget jobs, and projected overtime. Each day's digest is written once and a rerun adds nothing. Email delivery is not part of this yet.

Lead conversion by source

For any date range in your workspace's timezone, see how leads convert by source and service line: how many were contacted, estimated and won, with the count behind every rate and the value of the estimates that were accepted. Also see the estimate value still awaiting a customer's reply, the open leads not yet contacted, and the value attached to aging open opportunities by age.

Lead response time reporting

The first time you log or send an outbound email, call, or text to a lead, or complete a task linked to that lead, its first contact is recorded once. Average, median and worst response time, and open age for leads not yet contacted, are reported by person and by source over any date range, in calendar time.

Lead routing rules

An Owner can configure how incoming leads get assigned — round robin, by team, by territory, by service line, or to whoever is on a published shift — and can list, edit and disable those rules in priority order, against the same real assignment tables every actual assignment is made from, and every assignment records the rule that chose it.

Lead-generation request pipeline

Request lead generation from your connected provider — define the customers you want, track delivery against your request.

Lease terms and renewals

Track each lease you manage — property, unit, resident, owner, rent, and its end date — and bind a scheduled workflow to that end date so a renewal reminder fires the number of days before it you choose, commonly the weeks-in-advance notice period your lease requires. An on-demand owner statement totals expected rent for any period you choose from the same lease records, for the properties one owner holds. The Forge is not a property-management system of record: it holds no property/unit inventory, no application/screening pipeline, and no trust accounting, and it does not auto-generate rent invoices.

Lifecycle workflow triggers: customer inactivity, enrollment status, renewal due

Workflows can start when a customer has gone a set number of days without a completed job, when an admissions application or program enrollment changes status, and when a renewal reaches its lead time. Each one fires once per lapse or once per status change. Its actions are tasks, notifications and alerts, plus customer messages once the owner turns sending on for that workflow; a marketing message needs the customer's explicit opt-in on record, and a message that falls in quiet hours is held for the next window rather than dropped.

Live clock-in view for managers

Owners, General Managers and Operations leads see who is clocked in right now: each person, their job, their unit, how long they have been running and their week's hours with an overtime warning. The list refreshes on its own every 30 seconds while the page is open and shows how old it is. Employees cannot see it, and a unit-limited manager sees only its own units.

Live crew location and ETA

Crew members can share their location from the Forge app or a phone browser. Sharing starts only when they tap Share my location during an active shift or transport run, and a position is sent about every 30 seconds. It stops when the shift or run ends, when they tap Stop sharing, or after 14 hours. Positions are kept for 30 days. Managers see live crew positions and the estimated time to each crew member's next job on the dispatch board, as a list. Moving a job to another crew member or a new time sends that crew member a push notification right away. Guardian late notices use the live estimate when a crew position exists. Limited release.

Location launch playbooks and rollout of proven workflows

An Owner can keep a launch playbook for a company (an ordered checklist, proven workflows and message templates) and roll it out to any of that company's units. Each unit receives its own copies, so later edits to the source do not change them. Copied workflows start as drafts that an Owner switches on for that unit. Rolling out again copies nothing twice, and a failed step can be fixed and re-run from where it stopped. Customer, job and other business records are never copied.

Marketplace activation preview

Before enabling a marketplace add-on, its business/entity, billing account, immediate charge, recurring effect, usage basis, approval requirement, and provider are shown up front. Activating one is a separate, deliberate step: the price is the one your account team actually agreed — the catalogue's own figures are indicative and are never used as a quote — and it takes a second Owner or Finance approver, never the person who requested it, unless you are the only such user on the account. An active add-on appears on your monthly statement at that agreed price. Activation itself never charges a card: the statement stays informational, as every line on it is.

Church ministries and per-ministry access

Limited release, through the API only. A church can set up its ministries (children, care, worship, guest welcome and general) and give each staff member access only to the ministries they lead, through per-ministry grants. A revoked grant stops working on the next request. The ministry screens are not yet built.

Missed check-in alerts

A scheduled job whose crew has not arrived by the end of its arrival window creates one same-day task for your office. A clock-in against the job or an arrived tap confirms arrival. Limited release.

Per-location P&L and comparison

Revenue, labor cost, and the operating expenses recorded for each location, shown side by side across every location in the group. A location with no recorded expenses shows operating cost as not recorded, not as zero.

My shifts and hours

See your own upcoming shifts and the hours you have logged, drawn from the shift and time records your business already keeps in The Forge — not a separate copy. An open clock-in is shown on its own and is never counted into a weekly total, because there is no honest hours figure until you clock out. If your login is not yet linked to a staff record, the Hub says exactly that rather than showing an empty list. Weekly totals use ISO weeks in UTC. That link is no longer a dead end: accepting a team invite now links or creates your staff record automatically, and an Owner or General Manager can link, unlink, or create one by hand under Team at any time.

Native Mode onboarding provisioning

A new customer's onboarding answers determine which native operating modules are enabled from day one, with Forge itself declared as the system of record — not left ambiguous until a connector is set up.

On-time completion and turnover timing

Each completed job is marked on time or late against its scheduled end, with a 15 minute grace, and that flag is fixed at completion so later schedule edits do not change it. Weather-delayed jobs are reported in their own group. Completed and scheduled jobs are broken down by crew, service line and property, and turnover jobs show the time from request to crew assignment to completion, using the workspace time zone.

Online self-booking

Turn on a public booking page for your business, define the services and hours you offer, and let customers request an appointment online — requests land directly in your scheduling queue, and confirming one creates the job automatically. No separate booking tool needed.

Operational resources (locations, assets, vendors)

Track the locations, physical assets — with warranty and service-interval dates — and vendors — with insurance and certification expirations — your operations depend on, plus a three-way match between a purchase order, its receipts, and the vendor invoice.

Outbound messaging layer (shared send path)

Every outbound text and email now goes through one send path. Before anything is sent it is checked against the customer's opt-out, consent and quiet hours, and each send carries an idempotency key so a retry after a timeout never delivers the same message twice. Every attempt, including a blocked one, is recorded in the customer's communications history. Email goes from your own connected Gmail or Microsoft 365 mailbox when one is connected, and from the platform provider otherwise; your business can switch that routing off. Text messages stay queued with the reason shown while no SMS provider is connected.

Outbound webhooks

Register an HTTPS endpoint and choose which platform events it receives. Every delivery is signed with a standard HMAC scheme, retried on a published fixed schedule (5 seconds, 30 seconds, 2 minutes, 10 minutes, 30 minutes, 2 hours, 6 hours, 24 hours) if your endpoint is unreachable, and every attempt is visible in the deliveries list. An endpoint that fails ten deliveries in a row is disabled automatically and you are notified in-app. Deliveries never go to private or internal addresses or to non-HTTPS URLs.

Review, referral and renewal outreach cadences

After a completed job the Owner chooses whether the customer gets a review request or a referral request, and how many days after completion it is sent. Before a service agreement renews, the customer gets a renewal reminder, and a review invitation on the renewal date. Each request goes out at most once. Every one is sent through the same send path as other messages, so opt-outs, consent and the workspace quiet hours are checked first. Cadences are off until the Owner switches them on; while they are off nothing is queued or sent.

Overtime by location

The overtime report shows overtime by location. Each worker's overtime is worked out for each week first, then shared across the locations where that worker logged time that week, in proportion to the minutes at each location. A time entry's location is its job's location, or the worker's home location when the job has none. Time with neither is shown as unassigned. An account limited to specific locations sees only the time in its own locations, so a worker's overtime can read lower there than across the whole company.

Real-time overtime alerts

While a pay week is still open, managers see each employee's projected overtime from recorded and scheduled hours, with projected cost, and each employee is warned once per week before a daily or weekly overtime threshold is crossed. Overtime cannot yet be shown by location.

Business overview & wins

Income, outstanding invoices, labor cost, sales pipeline, and a simple 3-month run-rate projection are pulled into one daily overview from your own native records — real wins (a paid invoice, an accepted estimate, a completed job, a new customer) surface as they happen, and the single most useful next action is called out. The projection only appears once at least two months of paid-invoice history exist, and every figure here is computed from records you already have — nothing is estimated or fabricated when the data isn't there yet.

Panel schedules & versioned PDF documentation

Panel schedules are kept per job: each panel has a name, a location and a list of circuits with the circuit number, description, pole count, breaker rating and wire size, and the circuits are searchable. Each render saves a PDF of the schedule to the job as a new numbered version, and earlier versions are kept. The PDF is documentation only. The Forge does not calculate loads and does not check any code requirement.

Passenger transport: rider manifests and routing

Riders for a church, school or other bus or van service have pickup and drop-off addresses, accessibility needs (wheelchair, car seat) and, for minors, guardians and an authorized pickup list. A transport route has a vehicle, a driver, a capacity and wheelchair spaces, and enrolling a rider past either limit is refused. Buses and vans can both be routed. Each run has a manifest showing who boards, at which stop and the expected time, and the driver marks each rider boarded, dropped off or absent. Stops follow the distance from rider addresses, starting and ending at the depot and venue, and riders without coordinates are listed as needing a location. A run that ends with a rider not dropped off or marked absent raises an in-app alert. Stop order uses distance estimates, not live traffic. Guardian messages (text or email) are off until an Owner turns them on and texting or email is set up. Once they are on, a guardian who has agreed to transport notices (recorded at enrolment or by staff) gets texts that say the bus is on the way with an estimated pickup or drop-off time, that a rider is running late (estimated), and that a rider was dropped off, each only if the guardian wants that type; a staff member can also send running-late or not-picked-up notices by clicking Notify guardians. Guardians can change their preferences from a link, and a STOP text stops all texts. Consent, opt-out and quiet hours apply, and the drop-off notice may bypass quiet hours if the Owner allows it. Estimates come from the planned stop order, not live traffic. Limited release.

Payment processor integration

Once a business connects its own payment processor under Integrations, a native invoice can get a real hosted checkout payment link an Owner/GM generates and sends themselves — the customer pays with a card and the invoice flips to paid automatically once the processor confirms. Payment always runs on your business's OWN connected processor account, never the platform's. Stripe is the first supported processor. This does not cover Forge's own subscription/usage billing (see business-api.subscription-lifecycle / usage-metering), which is still not automatically charged.

Automatic invoice payment reminders

Unpaid invoices past due can get a reminder email on a schedule you set. Each reminder is logged, and no reminder goes out once the invoice is paid.

Payroll export with job allocation

Export approved hours to a payroll CSV for a chosen pay period. Each hour is allocated to its job and split into regular and overtime, using your overtime settings and your local time zone. Only approved hours are exported. Pending and rejected hours are listed and left out. Each exported hour is locked, so exporting the same period again never duplicates it. When an exported hour is corrected, withdrawn or removed, the next export carries a reversal of what was exported, so the totals across exports match the approved hours. The Gusto-shaped file is checked before it is made: a row without an employee mapping, without a job, with an unknown pay type or with a bad date is refused and listed. Hours already in an earlier Gusto file are listed as manual Gusto adjustments and left out of the file. Owner and Finance only. The Forge does not run payroll, withhold tax or move money.

Customer portal feedback inbox

Staff can read and reply to the feedback and support messages your customers send through their customer-portal link, and triage each one — the staff side of the same conversation the customer sees in their own portal.

Portfolio schedule board

The schedule board shows every active dated job across your companies, in one list. Each job shows its crew's overlapping jobs as a conflict. Finish-to-start dependencies between jobs show the slack in days and flag a successor whose predecessor now runs past its start, or whose predecessor has a weather delay, and every job further down a chain from a weather delay. You add and remove dependencies from the board. Moving a job never moves its dependents. A dependency that would create a loop is refused and nothing is saved. Subcontractor bookings show as their own lane with the job they are on, and an overlapping booking is flagged. Project milestones show as dated markers on the board.

Programs, class sessions & attendance hours

Run a course or programme where many people attend the same scheduled session, which nothing else in the platform could do — bookings and jobs each hold one customer per slot. Define a programme with the number of hours it requires, schedule its sessions with a seat count, enrol participants against a referral and a case reference, and track how many minutes each person has actually completed against what they owe. Attendance is an append-only record: a correction is written as a new entry that supersedes the earlier one rather than overwriting it, and both stay readable, so a changed figure can never quietly replace the original. Every entry records where its number came from — pulled from a meeting provider's own report, entered by staff, or reported by the participant — and the totals show separately how many minutes came from a provider rather than from someone typing. Attendance recorded from the live video room is pending staff verification until staff lock the session; room access alone is never credited. The completion gate requires verified minutes only when the programme's require verified attendance setting is on; when it is off, an enrolment completes on the minutes recorded, except live-room and provider minutes on sessions staff have not yet locked, which never count. The live session room needs a video engine (LiveKit) switched on for the workspace; until then the room opens and access is logged, but no minutes are credited from it and no video is shown, and sessions can use an external meeting link (Zoom, when connected) instead. The Programs screen lists each course and its sessions, shows the roster and every participant's hours with their source, and opens the session room.

Progress billing from accepted estimates

Bill an accepted estimate in stages. Each progress invoice is drawn from the estimate and the total billed cannot exceed the estimate's amount.

Property care instructions (versioned)

Each customer property can carry structured care instructions. Every edit is kept as a new version, and the crew assigned to a job at that property sees the current version on that job.

Portfolio occupancy, vacancy and turnover

Occupied, notice-given and vacant units across the portfolio, with days vacant and vacancy and turnover rates by property and by unit type. The page refreshes every 30 seconds while it is open. A unit appears once a lease names it, so units with no lease are not counted yet.

Provider service jobs

A service provider you activate from the Marketplace can perform document reading, browser rendering, and site-data lookups on your behalf. Every job is metered per unit at the price you agreed, shown on your statement, and never charged beyond a funded wallet. With no provider activated these features honestly show as unavailable.

Public self-booking page

The public page a customer actually lands on to request an appointment — deliberately reachable without signing in, since the person requesting time is not a Forge user.

Public job status page

A customer can open their job's shared status link to see the schedule and confirm it or request a change — the same public, unauthenticated page family as an emailed estimate or invoice link.

Punch list & closeout gate

Punch-list items on a project are tracked from identification to verified fix, with the fixer and a different verifier recorded and every step kept in the item's history. A final draw cannot be approved or paid, retainage cannot be released, and a project cannot be closed while any item is still open; the system answers with the list of open items.

Purchase orders linked to jobs

Tag a stock purchase order with the job it is for, so the materials you order can be traced back to that job.

Qualification-based technician dispatch

Jobs that require a specific license or certification are flagged, and dispatch only offers a job to technicians whose recorded, unexpired credentials cover it. A shift tied to a job cannot be assigned or published to a technician who does not qualify.

Real Estate & Brokerage lane

Contacts, properties, listings, deals, contingency milestones, and lead routing live in one workspace that integrates with - and never replaces - your MLS and transaction-management platform, which stay the systems of record for listing syndication and contract execution.

Receivables aging by account

Open invoice balances grouped by customer and by days past due, in current, 1-30, 31-60, 61-90 and 90+ day buckets, with totals.

AI Voice Receptionist operating surface

Every call the receptionist add-on handles - live, missed, or voicemail - lands in one queue with caller identity matched to your contacts and leads, a transcript, qualification notes, routing decisions, and per-call cost, so nothing arrives and disappears. Booking an appointment creates a real Google Calendar event when a qualifying Google connection exists, and creates a follow-up task either way, never a fabricated calendar confirmation. A slot that overlaps an open job for that technician is refused with a conflict, and nothing is booked and the call stays open. A missed call's follow-up task is due now during your business hours, or at the next business morning after hours (location hours when set, otherwise Monday to Friday 08:00-17:00 in your timezone). A default intake script and qualification framework is available via the API — see the "business-api.receptionist-persona" entry.

Recurring invoice schedules

Set a customer's invoice to repeat weekly or monthly. The platform creates each period's invoice on schedule from its scheduled sweep, and you can pause or resume a schedule at any time.

Recurring service visits

Recurring service agreements create their upcoming visits automatically, each as a draft job for you to review and assign. A visit is created once per due date, so a rerun never duplicates it.

Recurring visit billing and skipped-visit exceptions

Recurring service visits are billed once: each completed visit lands on one draft invoice in one billing period, and rerunning a period never creates a second invoice. Visits that were cancelled are listed as exceptions for office review and are never billed.

Renewal calendar across policies, leases and agreements

See every insurance policy, lease, service agreement, contractor licence or bond, and employee certification or driver credential end date in one calendar, grouped by business, ordered by how soon action is needed. Owners assign an owner and a 30, 60, 90 or 120 day lead time to each insurance policy, lease and service agreement, and the Forge opens one renewal task for that owner when the lead time is reached, moving the task if the end date changes. Licence, bond and certification dates are shown with their window and next step, and are tracked on their own records. Each person sees only the businesses they are granted. Renewal tasks stay inside the Forge; nothing is sent to customers.

Renewal outcomes and retention reporting

Record each renewal as renewed, lost or pending, with the contract value. The Forge reports the renewal rate for each month and service line, showing the renewed and due counts behind it, along with the revenue retained and lost. Renewing an agreement, policy or lease also starts the next renewal cycle.

Retainage release flags at substantial completion

A project records its contract substantial-completion date. Once that date passes, its paid retainage is flagged as eligible for release, the project shows how much is collectible now, and a draft release invoice for that amount is created for a person to review. Nothing is sent, charged or posted until someone approves it. Only an Owner, General Manager or Finance user can release retainage, and release is blocked while the project has open punch-list items. When your business turns on approval for adjustments (off by default), each release also needs a second approver: a different Owner, General Manager or Finance user.

Forward revenue pace from booked revenue

For the coming weeks and months, shows the revenue already booked (scheduled and in-progress jobs, recurring visits, fixed-fee billing schedules and acknowledged change orders) on top of what has been invoiced so far in each period, next to the same period last year. Every figure lists the rows it is built from, and accepted estimates with no scheduled job are shown as unscheduled, not added to a month.

Revenue recognition

Businesses running the native general ledger can defer and recognize revenue over time instead of booking it all on invoice issue — straight-line proration, percentage-of-completion you report period by period, or milestone recognition tied to a job's status. Each recognized period posts a real Deferred Revenue / Service Revenue journal entry, and profit-and-loss can be viewed on a cash or accrual basis.

Reviews & reputation loop

Every review shown in your dashboard or on your embeddable review widget is sourced directly from your own connected Google Business Profile — The Forge never posts, edits, or replies to a review anywhere on your behalf. Review requests are sent by email to a specific customer, only after checking the same consent/suppression rules that govern every other outbound message on the platform, and automated flooding is blocked so the same customer is never asked twice in a short window. You choose exactly which reviews appear on your public widget; nothing is shown there without your explicit opt-in.

Route runs for recurring visits

Recurring property visits go onto a crew's route for the day, in the order you set. Each crew member sees a work order before leaving: the stops in order, the checklist for each visit, and the property's care instructions. A stop is completed once its required checklist items are done, and a completion replayed from an offline phone is recorded once. Re-sequencing never moves a stop the crew has already completed. A route map and weather-aware scheduling are not built yet.

Saved replies in live chat

Keep standard answers to common questions in one shared list and drop one into a live chat in two clicks, or type a slash shortcut. A saved reply is only inserted into the reply box; you review it and press Send yourself. Customer, business and agent names fill in automatically.

Saved views

Save a named arrangement of a list — its sort, filters, grouping, and which columns are hidden — and reopen it later instead of rebuilding it every time. Keep a view private to you, or share it with your workspace read-only: only the person who made it can rename, change, or delete it. One view per list can be your default. Counts per plan: 10 (Start), 40 (Core), 150 (Pro), 500 (Operations).

Seasonal crew planning

Seasonal crew rotations can be previewed before anything changes. On the Jobs & Dispatch screen a dispatcher picks recurring visits and a new crew member, and sees each crew's shift minutes, booked minutes and open minutes per day before and after the move. Over-booked crews are flagged for review, not blocked. Only the owner confirms, and the confirm is all-or-nothing: a rotation whose visits or jobs changed after the preview is refused and nothing moves. Confirmed visits join each crew's route run for that day. Route history lists the moves and shows days late only for stops that were completed. Limited release; route-wide capacity by season and automatic rebalancing are not built yet.

Seasonal demand history and pre-booking window

Owners can see how many jobs were booked per week or per month, split by service line, counted from their own job records. An owner can also open a pre-booking window for a season, so customers can request times in that season before the normal booking horizon. Customers can book those times only once the window opens, and a time that is already taken is refused. History only: no demand forecast is shown, and no messages are sent to customers. API only; no screen yet.

Job engagement tracking

A customer engagement moves through its own stage pipeline, from inquiry through paid and renewed, with versioned estimate options and a recorded customer authorization for the option selected — separate from a job's own basic status lifecycle.

Service request inbox

Service and repair requests sent from your customers' portal land in one staff inbox, where your team can review each one, add internal notes, and convert it into a job.

In-app class room

Your class sessions get a room inside your own workspace, so a participant opens their portal and joins from there instead of being sent off to another company's website. The room decides who may enter on the server: an enrolled participant can join from fifteen minutes before the session until thirty minutes after it ends, a facilitator can open the room at any time to set it up, and a cancelled session or an ended enrollment is refused. Every entry AND every refusal is written to an access log with its reason, so if someone tells you they could not get into their class you can see exactly what happened and when. Live video is a separate switch that is not on yet: the room opens, checks the person in, and says so plainly rather than showing an empty screen. Nothing the room records counts as attendance hours — that ledger only accepts a measurement, and being admitted to a room is not one.

Site Health

Link the website your business owns and request a Site Health audit — an SEO pass and a passive security and trust pass (security headers, TLS certificate, cookie flags, email authentication, mixed content, exposed artifacts) run by a connected service provider, returned as evidence-backed findings in plain language. The audit is strictly passive and GET-only; a small number of extra benign requests run only against a hostname you have proven you control. Nothing is scored, graded, or reported that the site did not literally show.

Onboarding snapshot bundles

Named onboarding-accelerator bundles apply an industry starter pack plus starter communication templates and intake forms in one step — through the same create paths and plan limits as building each piece by hand, fully editable after and safe to re-apply.

Stage-based job messages and customer status link

Automatic messages can follow a job through its stages: a booking confirmation, a reminder a set number of hours before the visit, an on-the-way notice when the crew starts, and a completion notice. Stage messages are off until the Owner switches them on, each stage also needs its rule on, and each message goes through the same opt-out, consent and quiet-hours checks as any other message, and each stage sends at most one message per visit. Customers get a read-only status link that shows only their job's stage and appointment window.

Stalled item escalation rules

An Owner sets rules for items that go quiet: an untouched lead, a quote sent with no reply, a renewal coming due with no owner action, a follow-up that is overdue, or a job stuck in one stage. When an item sits past the window you choose, the Forge opens a high-priority task and an in-app notification for the manager or owner role, once per stall. The escalation closes automatically when the item moves. Nothing is sent to customers by email or text.

Short-term rental booking calendars drive turnover jobs

Paste a property's Airbnb, VRBO or Booking.com calendar link and each booking becomes one turnover job, dated the checkout day at the property's turnover time in your business timezone. A checkout followed by a same-day check-in is flagged. If a guest moves a booking, the job moves until a crew starts it; a cancelled booking flags its job for review and is never deleted. Host blocks on the calendar are ignored. On by default for every workspace; the Owner can switch it off.

Subcontractor portal (scoped sign-in)

Your subcontractors sign in through a single-use invite link. Your office either copies the link to them or emails it to an address you name, and an email goes out only when someone clicks Send. They see only their own engagement, the project it is on (name and status), and their own compliance documents with the expiry window of each. They can submit a compliance certificate for your review; nothing counts toward compliance until you accept it. Revoking a subcontractor's access ends their session immediately. A required compliance document that enters the 30, 60 or 90 day window, or lapses, emails its subcontractor one notice per window at their contact address; with no email sender connected the notice stays queued and is not shown as sent. Not built yet: subcontractor schedule, and draw amounts.

Subscription downgrade & cancellation

An Owner can request a plan downgrade or cancellation from within the account; a two-step confirmation is required and the change only takes effect at the end of the current billing period, never mid-period.

Post-visit surveys (NPS / CSAT)

A one-question survey is sent by email after a job completes or an invoice is paid, only to contacts who may be emailed under the same consent and suppression rules as every other outbound message. A high score offers the customer your existing review link through its own consent check, flood protection, and de-duplication; nothing is posted anywhere automatically. A low score creates a follow-up task for the Owner or General Manager. NPS is shown with the formula it was computed from.

Internal team chat

Owners, managers, and employees on the same account can chat with each other inside the app — a shared workspace channel, channels tied to a specific legal entity for those with access to it, and direct messages between any two teammates. Messages are polled on a short interval, not delivered over a live socket, in this first version; no file attachments yet. This is separate from customer communications — nothing here is sent to, or visible to, a customer.

Time-entry approval queue

Closed time entries wait in an approval queue ranked by labor cost, flagged for early clock-ins, late clock-outs and missing rates. An Owner, General Manager, Operations lead or the worker's own manager approves or rejects them. Nobody approves their own hours, and every decision is recorded in the audit log.

Toolbox talks & required postings

Toolbox talks are recorded per project with the topic, the date and the company employees who attended. A repeat of the same talk on the same date is flagged for review, never merged into the first. Required postings are kept as a checklist per project with the location, an optional expiry date and an attached photo held in the evidence store. The Forge keeps these as records only: it does not decide whether a talk or a posting meets any legal requirement.

Unanswered customer thread alerts and open-thread report

When a customer writes by email or text and nobody replies within the window you set, the Forge opens one high-priority task and an in-app notification for the manager or owner role, once per unanswered episode. The alert clears when a reply goes out. A window can count only your business hours when your location has them set. An open-thread report lists every customer still waiting, with the team member who owns the thread and how long it has waited. Nothing is sent to the customer.

Unit-scoped customers, jobs and staff

Customers, jobs and staff can be assigned to one of a company's units. A unit-limited account sees only its units' customers, jobs, staff, invoices, estimates, insurance claims, field checklists, notes, photos, route runs, time entries and shifts, plus its units' equipment, vehicles, allocations, availability and overrides. An asset or vehicle with no unit is hidden from unit-limited accounts. Bulk shift publishing is all-or-nothing: a batch that names another unit's shift is refused and nothing is published. Copy-week, fill and coverage work on the unit's own shifts and staff. Clock-in and clock-out, time approvals, the time CSV export, the overtime and crew-utilization reports, and photo export and expiry lists are limited to the account's units. Company-wide job revenue is left out of unit-limited crew figures. The fleet overview, vehicle condition, damage and breakdown records, safety reports and loads are limited to the vehicles and jobs at the account's units; a load belongs to the unit of its assigned vehicle. A load with no vehicle yet is listed and can be opened by a unit-limited account, read only, so nothing is missed; assigning, routing and logging on it stay with the unit of the vehicle. GPS position and geofence events are readable for the account's own vehicles. Procurement is limited to purchase work on the account's jobs. Stock balances, stock locations and vendors are company-wide and read-only for a unit-limited account, unless the Owner turns on "Limit stock and vendor lists to each person's locations" (off by default); when it is on, balances and stock locations follow each stock location's unit, and vendors are those used on jobs at the account's units. The physical-inventory API (/api/stock) follows the same switch for warehouse, stock, movement, allocation, supplier and purchase-order reads, with warehouses mapped to units. The labor-digest report is recomputed over the account's units, and a time entry can be moved to another business only when its unit is the account's. The cross-business labor report counts only the account's units' time entries. Freight rates, fuel contracts and index prices, transport estimates, audits, the fleet dashboard, GPS provider connectors and ingest, and weather stay closed to it, because they have no unit. Labor-hour tagging is not part of this yet.

Usage metering & statement detail

Every metered add-on (starting with AI Receptionist call minutes) is recorded as it happens and priced on a monthly statement alongside the subscription line, credits applied, and provider cost shown separately. The statement is informational: no usage line is ever automatically charged, whether or not a payment processor is connected.

Industry starter packs

Industry starter packs seed ready-made automations matched to how your industry runs — applied within your plan's workflow allowance, fully editable after.

First-time visitor return tracking

Limited release, through the API only. Each guest visit is recorded and matched to a person, or held for review when the match is unclear, and guest follow-up is assigned and tracked. Church screens are not built yet, and return counts and joining a group are not available yet.

Volunteer shift confirmations and need fill rate

Limited release, through the API and the volunteer reply page only. Volunteers who are not on payroll are invited to an opportunity from their private link. Invitations stay queued, not sent, until a messaging provider is connected. The volunteer report and fill rate are not available yet. Church screens are not built yet.

Wallets

Lead and campaign wallets track funded and spent balances in an append-only ledger, and fund the marketplace add-on programmes you activate. A wallet is never credited by asserting an amount — that is refused outright. Balance arrives only from a card payment the platform's payment processor has confirmed settled, or from an audited operator credit, and every entry carries a per-transaction ceiling and a $0 floor enforced inside the write itself.

Watchers

Checks a page you name on a schedule you set (15-minute minimum), bounded and robots-respecting, and alerts you in-app and by email only on a real change or a threshold you set — every alert shows before, after, and the rule that fired. Counts per plan: 1 (Start), 5 (Core), 25 (Pro), 100 (Operations). Never bypasses a site's robots rules or a login.

Weather-delay rescheduling

A dispatcher declares a weather day, optionally for one area. Scheduled jobs that day are flagged weather-delayed, and each gets the next open slot that fits its crew's published shifts, its crew's other jobs and its equipment. Later jobs for the same crew that day move with it. Nothing moves until the dispatcher applies it, and applying re-checks each slot. A cancelled weather day reverses the flags. Customer delay notices are queued for sending; nothing is sent automatically. There is no weather forecast feed: the weather day is entered by hand.

Web Presence audit

A bounded, robots-respecting read of up to 25 pages of a site you name — every finding is an evidence-backed observation with plain-language fix guidance, scored with a deterministic published formula; an undetected signal is reported as not detected, never as a manufactured deficiency, and no AI is involved.

Push notifications (PWA)

Push notifications go only to a device where you personally turned notifications on in Settings and your browser granted permission. Nothing is ever sent to a device that has not opted in, and you can turn it off for that device at any time. Delivery is best effort over the standard encrypted Web Push protocol; a device that is offline or revoked permission simply stops receiving.

Feedback capture & status tracking

Submit feedback from anywhere in Forge — a bug, something missing, or a workflow that's just confusing — and track its status on a plain timeline from received to released. Vote on ideas that matter to you and browse the roadmap for items your Owner or General Manager has chosen to share with your whole team, organized under consideration / planned / building / shipped — votes affect display order only, never a decision made on your behalf. Clustering and prioritization behind the scenes are not part of this yet.

Accounting push sync (QuickBooks Online, staged)

For a QuickBooks Online company you connect, invoices and customers can be pushed from The Forge. Push is on by default and needs QuickBooks connected with sync direction set to push or both; your business can switch it off. Each send carries a request key, so a retry after a timeout does not create a duplicate. If a record changed on both sides since the last sync, it is held for Owner review rather than overwritten. Other systems are import-only today.

Automatic updates from connected financial systems

Updates arriving from your connected financial systems are verified as genuinely coming from that provider before anything is applied to your records.

Customer email sending connectors

Send customer email from your own SendGrid, Mailgun, Postmark or Amazon SES account. The Owner enters the credentials once; the platform encrypts them at rest, checks them against the provider with a live call before saving, and sends a test message to the Owner. Each provider's bounce and spam-complaint reports are accepted at an unguessable per-connection URL, with the provider's own signature checked where it offers one (SendGrid and Mailgun), and a bounced or complained address stops receiving sends from your business. Built and tested against each provider's documented API and webhook schemes, not yet against a live customer account. Amazon SES notifications are not yet checked against the AWS SNS signature.

Gusto connector

Connect your own Gusto account via OAuth using your own Gusto Developer app. The platform encrypts your credentials at rest, can verify the connection against your real Gusto company, refreshes access automatically, and lets you revoke access (including at Gusto) at any time. It reads your Gusto employees, jobs and payroll wage summaries. Limited release: you can also submit approved payroll hours from Forge into your unprocessed Gusto payroll. Forge writes to Gusto only after an Owner or Finance user approves the exact changes in a dry-run preview, and reversals of hours already exported are listed in Forge as manual adjustments. Gusto still runs the payroll; The Forge never withholds tax or moves money. Built and tested against Gusto's documented API, not yet confirmed against a live Gusto company.

Industry tool connectors (read-only imports)

Owners can connect a supply house price list, a load-calculation report, a code-reference extract, a claim estimate export, or an EagleView roof measurement report. Each import only reads what the tool exports and never writes back to it. Re-importing the same records adds no duplicates, and a failed import shows up in the integrations error queue.

Square POS connector

Connect your own Square account via OAuth using your own Square Application — the platform encrypts your credentials at rest, can verify the connection against your real Square merchant and locations, refreshes access automatically, and lets you revoke access (including at Square) at any time. This is read-only: The Forge never processes or refunds payments through this connector. Built and tested against Square's documented API, not yet against a live customer account.

Assistant grounded in your own data

Ask a question and get answers grounded in your own workspace data — structured search across your records, communications, tasks, launches, finance, integrations, and org setup, filtered to exactly what your role can already see, every result tied to a real record. Plain-language summaries appear only when an assist provider is configured; otherwise you see the matching records directly, never a guess.

Data retention and archival

Records are archived rather than lost, and permanent deletion is allowed only once the retention period your business sets for each kind of record has passed — with defaults you can change in Settings.

Role-based daily workspace

One role-scoped rollup for today — the jobs and shifts on your schedule, plus your open finance exceptions and purchase requests — filtered to exactly what your role can already see in jobs, shifts, finance, and stock.

Required completion evidence

A job can require a set number of photos and finished checklist items before it can be marked complete; a completion that is missing them is refused and nothing changes. Crews can tag each photo before or after, and a job can require a before and an after photo. Owners can set the completion proof once as the default for new jobs. Photos on a completed job are also copied into the durable evidence store, so they remain as completion proof after the 5-day field-photo window.

Crew lead resolution & photo walkthrough gate

Every job automatically has a crew lead — the scheduled owner if there is one, an Owner-chosen override, or otherwise the crew member with the most recorded training and skills — with the reason shown in plain language. An Owner can require a photo walkthrough on the jobs a specific person leads; when that’s on, marking that job complete requires at least one active field photo first, and the app explains exactly why if it’s missing.

Field notes and checklists

A crew working the same job can leave notes and tick off one shared checklist from their own accounts — everyone assigned to that job sees the same entries, so the checklist is the job's record rather than a private copy per person. Correcting an entry, including unticking an item, keeps the original as history instead of erasing it, and each entry shows who wrote it. Only the person who wrote an entry can correct or retract it. They can also attach photos to the job; each photo is kept for 5 business days, then removed to keep things fast, and the whole job's photos can be downloaded in one tap before they're gone. Not available yet: this is web-only with no offline mode.

Field quality verification

Crew members mark each item on a job's quality checklist as passed or failed, with an optional note and photo. Every mark stays on record, and the job's result is derived from those marks and can hold completion until they pass.

Job postings and applicants

Write up a job you are hiring for, open it, and track everyone who applies through a simple set of stages from new to hired. If you point one of your public forms at an open posting, anyone who fills it in becomes an applicant instead of a sales lead, and you are notified. Rejecting or withdrawing a candidate moves them to that stage rather than deleting them, so your record of who applied stays intact.

Interview panels and scorecards

Schedule an interview for a candidate, invite one or more of your team members as panelists, and let each panelist submit their own 1-5 score, a hire recommendation, and private notes once. Scheduling a panelist against a time window that overlaps one of their other interviews warns you before it books, but never blocks you from double-booking on purpose.

Offers, including hire conversion

Extend a candidate a real offer — role, pay, start date, and an optional expiration — and move it to accepted, declined, or withdrawn. Accepting an offer is what actually turns the candidate into an employee record and starts their entity-scoped onboarding checklist; nothing before this capability did that.

Hire-scoped onboarding checklists

Give a new hire a checklist grouped into documents, training, equipment, and first-week schedule, each item trackable as pending, done, or skipped with an optional due date. A General Manager sees exactly what's complete and what's blocking without ever receiving the private HR notes on an item — those stay Owner/HR-only, redacted server-side before the response is even built.

Employee recognition

Anyone on your team can give a teammate a public kudos tied to one of your company's values, and owners can hand out named awards and get reminded ahead of service anniversaries and birthdays — no gift-card economy, just visible appreciation.

Staff Library

Owners publish policy and training documents to the roles or positions they choose, and staff sign off with a drawn signature, a typed name, and an explicit consent checkbox — the signed record captures the exact version, its content hash, the time, and the device it was signed from, and can never be edited afterward. Owners, general managers, and HR see a compliance grid of who has and hasn't signed, get a daily reminder digest for overdue items, and staff themselves get a nudge to re-sign when a policy changes. This never blocks clock-in or any other part of the product; it is visibility and a reminder, not a gate.

Technician licence and certification records

Technician records carry their licenses and certifications with expiration dates. Owners verify each one, a document can be linked to it, and the person who manages the technician gets a task 30 days before it expires.

Evidence-linked control registry

An internal, evidence-linked inventory of the platform's security, availability, and confidentiality controls, mapped to SOC 2 Trust Services Criteria for every entry, so a third-party pen test or audit can be scheduled against known-honest evidence instead of a from-scratch discovery process. This is an internal control inventory only, not a certification — no penetration test or formal audit has been performed.

Evidence backup manifest & integrity

Every stored evidence object is continuously checksummed against its original hash and mirrored to a second, content-addressed copy in the same evidence bucket, so an accidental deletion, an accidental overwrite, or silent corruption of a single object is detected and can be restored by an account Owner. This does not protect against loss of the evidence bucket or the Cloudflare account itself — true off-bucket, off-account replication requires a separate, operator-provisioned second bucket that has not yet been provisioned.

Release-journey conformance evidence

The core signup-to-revenue workflow — sign in with MFA, connect a provider, take a call, route a lead, schedule an appointment, track a listing to close, approve and publish marketing, forecast commission, export records, and prove one brokerage cannot see another's data — is exercised end to end by an automated test on every change, with a dated pass/gap scoreboard, not just claimed in a slide.

Client-driven public roadmap

See what other businesses on Forge are asking for, ranked by how many have raised it — not a hand-picked marketing list. Say an existing idea matters to you in one click and it counts toward the same ranking. An idea only appears once more than one business has raised it, or the same business has raised it a few times, so no single client's private complaint is ever shown as if it were a trend.

Launch workspace aggregate

One view shows a launch's phase, milestones, owners, customer vs HustleForge tasks, risks, blockers, and pending approvals - each section only shows what the viewer's role can already access in its own module.

Forge Credit packs

Any plan can buy packs of Forge Credits (1 credit = $1) through the payment processor's hosted checkout. Credits are added only after the processor confirms the payment settled, exactly once per payment, and purchased credits never expire. They pay for published posts and extra content ideas where your plan charges for them. Requires the platform's payment processor to be configured; not yet validated with a live payment.

Daily idea deck & extra idea packs

A deck of ready-to-post marketing ideas - an image, carousel or short video with a caption and per-network variants - that you approve or skip one card at a time. Approving turns an idea into an ordinary post that goes through your normal approval and publishing flow. Forge Pro includes 20 ideas a day and Forge Operations 40, resetting at local midnight in your workspace's time zone; on any plan you can buy extra packs of ideas, and a pack that can't be prepared is never charged. The deck, approvals, limits and purchase flow are built and tested; the ideas themselves are prepared by a separately operated content service, so a deck only fills when that service delivers.

In-house image generation for social posts

Describe the image you want inside the social composer and a ready-to-attach image is generated for you, sized for the post. The generate control only appears when the image service is connected, and a service problem shows an honest unavailable state — never a false success.

Content calendar, broker approval & scheduled publishing

A post moves through broker approval before it can ever be scheduled, and every attempt to publish is tracked with an honest status - published, or a specific reason it could not be, never a false confirmation. OAuth orchestration and the Facebook/Instagram/LinkedIn/X provider adapters are built and tested against each provider's own documented API; a business can connect a channel today with their own app credentials, and Facebook/LinkedIn additionally support HustleForge's own platform-default OAuth app once the operator provisions the required secrets and Meta/LinkedIn app review clears - no live-account validation has happened yet either way.

In-house Reel (video) generation for social posts

Choose 1-4 images already generated or attached, add a caption for each scene, pick a duration, and a ready-to-publish vertical Reel (1080x1920, Facebook and Instagram) is composed for you. The generate control only appears when the video service is connected, and a service problem shows an honest unavailable state — never a false success. Generation is metered against the same monthly media allowance images use, at a higher per-second cost, never free-unlimited.

Capability-gap assist guidance

When a user hits a permission or feature boundary, the platform can offer contextual guidance from a configured assist provider.

Telephony provider webhook adapter

Call events from your configured telephony provider are verified and normalized into the receptionist queue automatically - this platform's own code path is real, but whether calls actually arrive depends on your provider being connected and configured to send them here.

Physical inventory capability discovery

The platform can report which physical-inventory capability packs a workspace has available. Item tracking and a usage-based ordering estimator are now live under business-api.inventory-tracking (Pro) — see that capability for the real feature; this one remains pure pack-discovery metadata.

Admissions document checklists and missing-item follow-up

Each application lists the materials it requires and tracks each one as received or outstanding, so missing items are followed up automatically. Not yet built: admissions applications hold no per-item checklist.

Enrollment funnel stage conversion

Shows every prospective family by stage, from inquiry through tour, application, offer and enrollment, with conversion rates between stages. Not yet built: lead and application stage counts are separate and no conversion is calculated.

Application checklists and missing-item follow-up

Each application carries a checklist of required information, and missing items trigger a follow-up before the quote is prepared.

Backorders and fill rate

Short-shipped order lines are flagged as backorders with a customer notice, released for shipment when inventory arrives, and reported as fill rate and backorder aging.

Catering and event bookings

A catering inquiry becomes an event booking with menu selections, headcount, deposit status, and staffing needs, followed through to the event and final invoice, with a pipeline of open and confirmed events.

Client deliverable approval requests

Submits a deliverable for client review, sends a structured approval request, captures the response on the engagement, and escalates when approval stalls. Not yet built: no deliverable or approval-request record exists and engagements have no stall escalation.

Donor stewardship milestones

Flags first gifts, increased giving and lapsed donors so stewardship follow-up starts from the giving record. Not yet built: the only milestone is a date offset from a gift's received date.

Engagement profitability rollup

Rolls revenue, logged hours and cost up to each engagement while it is still open. Not yet built: job economics roll up per job and engagements are not linked to a rollup.

Engagement renewal forecast

Lists engagements approaching their end date with a renewal likelihood and the revenue at risk if they do not renew. Not yet built: renewal dates trigger workflows but no forecast or revenue-at-risk figure exists.

Engagement scope, timeline and billing terms

Holds the scope, timeline and billing terms on a signed engagement, and records scope changes with client acknowledgment before billing is adjusted. Not yet built: service engagements have stages and estimate options but no scope, timeline or billing-terms fields.

Retention and book composition

Renewal rate by producer, line, and client segment, and policies in force by line, carrier, and premium band.

Bind and policy servicing

An accepted quote converts to a bound policy on the client record, and endorsement requests, certificates, and claims are tracked against that policy.

Customer e-signature approval of change orders

Planned: a customer will approve a change order by e-signature through the existing signature flow, and the signed approval will acknowledge the change order automatically. Until this ships, change orders are acknowledged by staff.

Maintenance requests and work orders

Renter-submitted maintenance requests, from the portal or an inbound email, become work orders routed to a vendor or technician, track status to renter-confirmed completion, and escalate when they stall.

Order intake to fulfillment

Orders from reps, phone, email, or EDI are captured on the customer account, priced at the account's pricing tier, checked against credit status before confirmation, and routed to the warehouse for picking, packing, and shipping.

Practice pipeline reporting

Unscheduled treatment value by provider and case type, and new-patient conversion from inquiry to booked to first visit, by source and month.

Transaction milestone deadline alerts

Flags a transaction milestone that is approaching its due date or is at risk, and alerts the agent and transaction coordinator. Not yet built: milestone due dates are not a workflow schedule source, so milestones are not flagged automatically.

Rent ledger and delinquency escalation

Rent charges post on each lease's due date, and a missed payment moves through your configured notice, follow-up, and escalation steps, with delinquency aging by property and renter.

Rental applications and screening

Rental applications are submitted, screened against the criteria you configure, and moved to lease preparation, with follow-up for missing documents.

Residence beds, stays and restricted period

Tracks beds by house, assigns each resident to a bed with start and end dates, records the end date of the restricted early period, and shows open beds and length of stay by house. Not yet built: there are no house, bed or stay records, so occupancy cannot be counted.

Scheduled report delivery

Reports will be sent by email on the daily, weekly or monthly schedule you choose, without anyone assembling them by hand. Planned. Not available today.

Superintendent daily log

Superintendents will log each project's daily progress, crew on site and conditions, and that log will feed draw checks and the project record. Planned. Not available today.

Tuition, aid and net revenue summary

Shows projected tuition revenue, committed aid and net revenue by grade level and enrollment status. Not yet built: invoices carry no grade or aid fields and no aid commitment record exists.

Public lead capture

A public endpoint validates a website inquiry and blocks bots and automated flooding before accepting it. It does not yet store or forward the submission anywhere, and no page in the product currently links to it.