BlueCotton
Commerce, ERP, production, scanners, and file exchange.
Order → production
A shared AI platform to build, operate, and continuously improve software around each customer's workflows.
The opportunity: make company-specific software scale through shared automation.
An order has to become production work. When tools and records disagree, people carry the process by hand.
Customer orders
Business records
Work in progress
Scanner workflows
Connected systems
Software shaped around the whole workflow, with one team responsible for keeping it useful.
Workflow illustration based on documented project scope. This is not a claim that every integration is live or that a specific customer ROI has been measured.
Customers get their own workflows. Handrail reuses the machinery that builds, checks, releases, and operates the software.
Customer requests + runtime evidence feed the next improvement ↺
Platform architecture drawn from Handrail's documented implementation contracts. Individual capabilities and automation settings vary by project.
Connect the request to the application, its existing workflow, and the user's authority to request work.
Use the project's code and development environment to implement the photo requirement across the relevant screens and business rules.
Verify the required behavior: closing a work order requires a photo, and authorized users can still complete the job.
Evaluate the accumulated release against the enabled environment's checks and policy. Add human review wherever required.
Record delivery and subsequent verification separately. Customer feedback and runtime evidence inform the next investigation or improvement.
Five named accounts from management's Won list. Their needs span commerce, manufacturing, field work, and service operations.
Commerce, ERP, production, scanners, and file exchange.
Order → production
ERP supporting office and field operations.
Office → job site
ERP, mobile work, and monitoring scope.
Alert → service
Purpose-built ERP for project operations.
Project coordination
Software for the memorial business.
Specialized workflowsDescriptions reflect documented project scope, not a statement that every component is in production. Five names are approved for this deck; the CRM includes one additional Won deal. Measured ROI is not yet available. Evidence notes ↗
$350.4K annualized CRM value
CRM stage: Won · billing and collections not reconciled hereSales and partnerships handled by one employee, without full sales focus.
A regional starting pointManagement reports essentially no formal marketing to date.
Monthly CRM values × 12. Won deal cards may not equal billing accounts. Open stages are neither signed revenue nor a forecast. The 12 open opportunities also carry $1.1M in potential one-time build fees. Definitions ↗
A scoped fee covers initial development, migration, and agreed integrations.
Recurring fees cover the live platform, support, and explicit allowances for change.
Price added capacity, agreed services, and separately operated deployments.
Recorded deal range across differing scopes.
Proposed tiers for 500–2,500 users, plus a $120K+ build.
Enterprise terms come from an unsigned reference proposal and include 40 engineering hours per month plus defined resource allowances. They are not achieved average pricing. Measure actual usage and direct costs by cohort; extra modules do not automatically create another deployment fee. Commercial basis ↗
Handrail applies AI across software's operating life: building the first version, responding to requests, investigating problems, and delivering the next release.
Shared deployment machinery, SDKs, integrations, and project controls.
Carry project context and evidence from request through delivery and continued operation.
Grow recurring accounts while reducing human effort per implementation and change.
This is the operating thesis and measurement framework. No productivity multiple or software-margin result is asserted.
Handrail keeps requirements, code, operating context, and change delivery connected under one accountable relationship.
| Customer alternative | What the customer buys | Where Handrail aims to win |
|---|---|---|
| Packaged suite + integrator | An established suite with implementation and customization. | A system shaped around the customer's operating workflow. |
| Development firm / internal team | Custom engineering and ongoing support capacity. | Shared automation that reduces repeated delivery effort. |
| App platforms Retool · ServiceNow App Engine | Tools to build, deploy, and govern business applications. | Implementation and continued operation in one managed offer. |
| Handrail | Company-specific software plus its continuing operation. | Project context + reusable platform + accountable delivery. |
Positioning, not a tested feature ranking; competitors and their partners can offer overlapping services. Sources: Retool ↗ · ServiceNow ↗. Validate the advantage through customer choice, delivery cost, and retention.
Roughly 50–500 employees.
Owner or operations leader, with finance and IT involved.
A core workflow has outgrown the fit of packaged tools and spreadsheets.
Lead with an industry workflow demo and named customer references. Track sales cycle, conversion, and delivery effort.
Grow from one process into adjacent departments, sites, and business units with separately agreed scope.
Test an integrator offer that rewards the partner for customer discovery, delivery, and continuing account value.
Proposed initial focus based on the current account mix, not a measured market segment. Marketing supports the same focused offer with demos and customer evidence. No national conversion rate or signed partner channel is assumed.
The expansion path runs from a critical workflow to departments, sites, and enterprise business units—including work around existing suites.
in recurring fees
$58.4K annual recurring value per deal in the CRM snapshot.
$180K annual recurring fees per account, based on proposed pricing.
Rounded scale illustrations: $100M ÷ annual fee. They are not a forecast, account-count target, or TAM estimate. Current deal cards may not equal billing accounts; enterprise pricing is proposed. A count of eligible buyers and observed conversion are still needed to size the reachable market.
Handrail grew out of Hitcents' experience delivering software and supporting the systems behind it. Product, infrastructure, and customer responsibility meet in one team.

Company leadership and customer relationships.

Customer workflows and the product experience.

The environments and systems behind delivery.
A longstanding core team, now turning recurring delivery work into a shared platform.
History and divisional scale are management supplied. Historical organizational scale is distinct from Handrail's current staffing or enterprise sales performance.
Use capital to turn early customer wins into measured delivery capacity and a sales motion that travels beyond the existing network.
Referenceable deployments with launch time, human effort, direct cost, and customer outcomes measured.
Result: explainable account marginsSell the same focused offer beyond current relationships, with a documented funnel and delivery capacity.
Result: a repeatable sales motionTest partner incentives and joint delivery on a bounded offer before expanding the channel.
Result: evidence for channel expansionCompany-specific software.
A shared platform that keeps it moving.
Milestones describe the proposed next stage. Supporting definitions and open diligence items follow. Read the evidence notes ↗
Won: 6 cards, $29,200/month. Proposal: 2 cards, $25,000/month. Contacted: 10 qualified leads, $83,000/month. Annualized values multiply monthly fees by 12. Open pipeline is unweighted.
Won does not establish subscription commencement, billed ARR, or collections. Reconcile signed, live, invoiced, and collected amounts before using those labels.
Won CRM fees range from $2K to $10.5K/month. An unsigned enterprise proposal specifies a $120K+ initial build, $15K–$27.5K monthly tiers, 40 engineering hours, and resource allowances.
Reference pricing is not achieved average revenue. Actual engineering usage, infrastructure, AI, and support costs are needed to establish margins by account.
Customer names are approved; descriptions summarize documented project scope. The platform diagram and example walkthrough describe Handrail's operating model, not a captured live run.
No validated customer ROI or automation productivity multiple is claimed. Capabilities and release checks depend on each project's configuration.
The reference proposal names Hitcents as contracting party and application/platform software owner; customers own their data, materials, and outputs.
The investment entity's rights to IP, contracts, and economics need definition. Management's “cash-flow healthy” statement needs entity-level reconciliation; no standalone Handrail cash-flow figure is presented.
Next evidence: customer outcomes · account margins · sales conversion · financing structure.
Back to the investment case ↗