The process does not fit.
Packaged software imposes its workflow. Teams add manual steps to handle how the business actually works.
Cost: duplicate work and missed information
01 / The business 36-month operating plan
Enterprise software.
Built for the way
you operate.
An enterprise software factory that uses AI and experienced engineers to build, run, and continuously improve custom business systems.
Build around the businessOperate with release controlsImprove as needs change
02 / The enterprise problem
The business changes.
Its software falls behind.
Critical work ends up spread across a core system, disconnected tools, and spreadsheets. Every change must preserve the operations already running.
The replacement is a project.
A custom build needs requirements, integrations, data migration, testing, and people accountable for launch.
Cost: a long path from need to daily use
The work never stops.
Once live, permissions, reports, business rules, and integrations keep changing. A fast first build is only the start.
Cost: a permanent maintenance burden
The customer needs a system that fits—and a team responsible for keeping it working.
03 / Productized hybrid model
Custom software outside.
A repeatable product inside.
Handrail productizes the operating system around custom development: one platform, reusable operating patterns, and an accountable delivery team.
Platform
Requests, scope, release evidence, environments, access controls, deployment policy, and runtime diagnostics.
Reusable across every accountOperating blueprints
Data models, roles, workflows, reports, integrations, mobile patterns, and device connections refined by vertical.
Reusable within the wedgeDelivery service
Discovery, migration, implementation, QA, launch, support, and a managed queue of approved changes.
Accountable to the outcome- Discover
Baseline the workflow and ROI.
- Launch
Build, migrate, test, and train.
- Operate
Host, monitor, support, and govern.
- Expand
Ship the next approved workflow.
The customer buys a working operating system—not developer seats or an open-ended software project.
04 / Competitive position
Between a tool and an agency.
Accountable for the live system.
The category gap is not code generation. It is converting a customer-specific workflow into a governed, supported operating system without asking the customer to assemble the team.
| Buyer requirement | Packaged SaaS | Low-code / AI tools | Custom dev firm | Handrail |
|---|---|---|---|---|
| Fits the operation | Business adapts to the package. | Customer assembles and builds. | Custom, project by project. | Custom workflow on a repeatable operating layer. |
| Who owns delivery? | Customer + integrator. | Customer’s technical team. | Vendor until handoff. | One team through build, launch, and operation. |
| Physical + digital work | Limited to vendor roadmap. | Possible; customer integrates it. | Possible; scope dependent. | Web, mobile, infrastructure, legacy, and device patterns. |
| Change after launch | Configuration or roadmap. | Customer keeps building. | New project or retainer. | Managed change queue with release evidence. |
The defensibility thesis: operational knowledge, reusable vertical modules, delivery data, integrations, and a trained implementation bench compound with each account. These are advantages to prove through reuse, retention, and margin—not a claimed moat today.
Tooling + team + operating memory05 / Customer evidence
Verified platform footprint5external operating
external operating
organizations.
Current Handrail records show five external organization contexts with real application and infrastructure work. Names remain private in this deck.
Custom manufacturing & commerce
ERP, storefront, production scanner, and managed file-transfer workflows.
Industrial & field services
Operational ERP with live-service health and backup workflows.
Managed operations · 2 contexts
ERP, web/mobile surfaces, sensor operations, and network monitoring.
Construction operations
A purpose-built ERP for project and back-office work.
Established
External operating contexts and production-class application work.
Not established here
Paying-customer count, ARR, ACV, contract term, renewal, or reference rights.
Investor diligence
Reconcile customer, contract, invoice, and permission records before circulation.
06 / Case studies and ROI
The footprint shows the wedge.
The scorecard must prove the return.
Turn three current implementations into investor-ready case studies by agreeing the baseline before launch and measuring the same operating result 30 and 90 days later.
Order to production
ERP + storefront + scanner / SFTP.
- Measure
- Order cycle time, manual touches, rework, on-time shipment
- Value
- Hours saved + errors avoided + throughput gained
Quote to closeout
ERP across office and job-site work.
- Measure
- Quote time, field entry lag, WIP visibility, days to invoice
- Value
- Labor recovered + faster billing + less leakage
Alert to resolution
ERP + web/mobile + monitoring.
- Measure
- Response time, support effort, billing accuracy, incident recurrence
- Value
- Service capacity + retained revenue + avoided downtime
Baseline 30 days of current workLaunch adoption + data qualityDay 30 early operating changeDay 90 validated ROI case
No Handrail ROI metric was available in the reviewed materials, so none is claimed. Category benchmark only: a 2026 Retool / Komatsu case projected 30–40% lower call-handling time and more than 22,000 hours saved annually; use it to design measurements, not as Handrail evidence. Source ↗
07 / Total addressable market
An established software budget.
A different way to serve it.
Enterprise application SaaS across businesses of all sizes.
Market segmentation · USD billions / yearIllustrative allocation, not measured segments
| Customer location | <500 employeesSmaller businesses | 500+ employeesLarger enterprises | All sizes |
|---|---|---|---|
| North AmericaU.S., Canada & Mexico | $39.3B | $59.0B | $98.3BModeled |
| GlobalIncludes North America | $87.4B | $131.1B | $218.5BSourced total |
North America
Global
<500 employees 500+ employees
Planning assumptions: North America = 45% of global; <500 employees = 40% of spend in each region; 500+ = 60%. The 500-employee boundary includes exactly 500 in the larger group. Regional and size shares are assumptions, not Gartner findings.
A dated category TAM, not a 2026 estimate or Handrail revenue forecast. Regions overlap; do not add the rows. Only part of this market fits Handrail’s offering.
08 / Market entry
Win specialty operations first.
Expand from the system of record.
Proposed beachhead: North American specialty manufacturers and field-service operators with 50–500 employees, fragmented operational software, and an owner, COO, or CFO accountable for the result.
Specialty manufacturing
& field service.
Complex quoting, jobs, inventory, field work, production, and billing—without a large internal product team.
- Buyer
- Owner, COO, or CFO with an operations lead
- Land
- One painful workflow or an operational backbone
- Proof
- Cycle time, error rate, cash conversion, adoption
A defined business unit.
A repeatable rollout.
Use the proven blueprint in a multi-site or multi-entity operator where IT can validate controls and integrations.
- Buyer
- Business sponsor with CIO / IT
- Land
- A bounded operation, region, or system
- Proof
- Reliability, deployment speed, and expansion economics
WedgeQuote / job / inventory / field workflow
→System of recordOne operating model across the business
→ExpansionMore sites, workflows, entities, and services
Why this wedge: it matches the current external project footprint and rewards Handrail’s web, mobile, infrastructure, device, and managed-delivery capabilities. The serviceable account count and spend still require a qualified target-account study.
09 / Commercial model and pricing
Price the outcome, operation,
and engineering capacity separately.
Fixed fee for agreed scope, integrations, and launch. Additional scope is priced separately.
One-time build revenue$15K/ month · up to 500 users
$20K/ month · up to 1,000 users
$27.5K/ month · up to 2,500 users
Hosting, support, and 40 engineering hours monthly, with defined allowances for change requests, infrastructure, and AI.
Recurring fees include services; user limits are not employee segments.Keep now
Paid implementation, annual commitment, production-readiness billing trigger, and reference subscription bands.
Test next
Quote platform / operating scope separately from engineering-capacity packs so heavy change demand cannot silently compress gross margin.
Measure before changing
Win rate, implementation effort, included-hours use, infrastructure cost, expansion, renewal, and willingness to pay.
Reference terms from the documented MSA / proposal review. This is pricing evidence, not achieved ACV. Preserve the current bands until delivery cost and win/loss data support a change; then standardize the package instead of discounting ad hoc.
10 / Revenue visibility
A pipeline is evidence.
Not a list of logos.
Report implementation fees and recurring commitments separately, with one dated definition for each stage and no revenue attributed before the evidence exists.
| Stage | Required evidence | Revenue treatment |
|---|---|---|
| Contracted | Signed scope, term, price, billing trigger, and target launch. | Booked build + committed recurring schedule. |
| Procurement | Commercial terms agreed; legal, security, or purchasing open. | Unbooked; show separately from contracted. |
| Proposal | Named sponsor, defined scope, price delivered, decision date. | Weighted only after conversion history exists. |
| Qualified | Budget, sponsor, operational pain, timing, and technical fit. | Coverage metric; not forecast revenue. |
| Discovery | Named account and problem; qualification incomplete. | Activity only. |
Booked implementation + committed feesCoverage qualified pipeline ÷ targetVelocity stage conversion × daysCapacity signed launches ÷ delivery slots
No auditable current pipeline value was available in the reviewed materials, so none is shown. The investor data room should include account-level stage, value, next step, owner, decision date, and delivery start; the deck should publish only reconciled totals.
11 / Implementation and service
Scale delivery capacity
alongside the sales team.
2implementation engineers
½ implementation lead½ QA / migration specialist
Three full-time equivalents per team, including shared specialists. The lead owns customer scope and launch; engineers own build and integration; QA covers migration and acceptance.
2 concurrent builds × 2 cycles / year= 4 launches per team annually
Assumes six-month implementations. Longer or more complex projects reduce capacity.
Keep capacity for the
customers already live.
60 × 40h= 2,400 engineering hours / month÷ 120hof customer delivery time per engineer / month20 engineersat full use of the included allowance
Initial builds, platform engineering, and customer support are staffed separately.
AI may reduce effort per change. Hiring follows measured delivery hours and quality—not an assumed productivity multiple.
12 / Integrated business economics
Connect the contract
to cash, capacity, and margin.
Reference implementation$120K+one time
+Mid-tier recurring fee$240Kannualized at $20K / month
=Illustrative first-year value$360K+only if 12 subscription months bill
Month 12 / 10 accounts$2.4MAnnualized recurring fees
Month 24 / 30 accounts$7.2MAnnualized recurring fees
Month 36 / 60 accounts$14.4MAnnualized recurring fees
Signed builds, subscription commencement, launch timing, expansion, renewal, and churn.
Implementation labor, included engineering, support, cloud, AI, third parties, and warranty work.
Collections, hiring dates, sales cost, platform investment, working capital, and contingency.
Targets are illustrative, not current results or backlog. Annualized fees are exit run rate, not earned revenue. At $20K monthly revenue, direct monthly costs of $5K / $10K / $15K imply 75% / 50% / 25% gross margin. The integrated model must be monthly and cohort-based before any capital amount is credible.
13 / Organization and capital model
A team sized for
booked work—not ambition alone.
| Function | Month 12 | Month 24 | Month 36 |
|---|---|---|---|
| Go-to-market | 4 | 8 | 12 |
| Implementation teams3 / 6 / 9 teams × 3 FTE | 9 | 18 | 27 |
| Recurring engineering40h allowance ÷ 120h capacity, rounded up | 4 | 10 | 20 |
| Customer success & support | 2 | 3 | 6 |
| Platform, infrastructure & security | 5 | 8 | 12 |
| Leadership, finance & operations | 2 | 3 | 4 |
| Total planned capacity | 26 | 50 | 81 |
Totals include existing or shared allocations; they are not incremental hires. Each role enters the cash model on its actual planned start date. Do not infer a raise amount or runway from the year-end headcount table alone.
14 / Team and durable advantage
Built inside a business
that knows software delivery.
Handrail was developed inside Hitcents, drawing on 25 years of building, launching, and maintaining software.
How the advantage compounds01 02 03
Operating memory
Customer rules, integrations, release history, and production evidence make the next change better informed.
Reusable delivery IP
Vertical data models, modules, connectors, tests, and migration playbooks shorten the next launch.
Platform + bench
Competitors must replicate both the operating platform and the accountable engineering organization.
Defensibility becomes credible when reuse lowers delivery cost, references improve conversion, and customers renew and expand.
15 / Use of proceeds
Stage capital against proof.
Fund the next constraint.
Capital accelerates a working platform. Each tranche should remove the constraint between signed demand and repeatable, profitable delivery.
Customer proof
Baseline measurement, adoption support, reference permissions, and three quantified case studies.
Focused GTM
Founder-led sales, vertical messaging, solutions engineering, and partner/referral development.
Delivery capacity
Implementation pods, migration/QA specialists, customer success, and recurring engineering.
Factory leverage
Reusable vertical modules, integrations, reliability, security, and release automation.
Tranche 1 proves
Customer ROI · pricing · implementation margin · sales cycle
Tranche 2 proves
Repeatable vertical conversion · renewals · delivery reuse
Growth capital scales
Only the channels and delivery model already supported by evidence
No raise amount is presented because the reviewed materials do not support one. Populate the monthly model, calculate peak cumulative cash deficit, add contingency, and compare a single raise with milestone-based tranches before setting the ask.
16 / The next diligence meeting
A working delivery system.
A focused proof agenda.
The next investor conversation should connect the live product to customer contracts, measured business results, pipeline evidence, and the monthly capital model.
Product demo
Request → scope → build → checks → release → runtime evidence.
Customer cohort
Count, revenue, contract terms, renewal status, and reference permission.
Case studies
Baseline, adoption, operating change, and validated dollar return.
Financial model
Pipeline, cohorts, delivery cost, hiring dates, collections, and peak cash need.
The investment thesis
Continue the conversation ↗partnerships@hitcents.comOwn the outcome for operations-heavy businesses.
Turn each custom system into reusable delivery leverage.
A Hitcents company · Bowling Green, Kentucky