Operations & Commercial Automation — Revenue First

1. Repositories under control

Core: Runway Fuel, ecowoods-app. Vertical applications: floorforge-ai, paintforge-ai, dryforge-ai, bahn-project-manager. Related: LogistiSync, equipment tracking, field-service software, contractor software, operational dashboards, relevant commercial websites.

2. Target architecture

Runway Fuel is the Operations OS. Applications sit on top: field service, contractors, logistics, industrial services, critical infrastructure.

• EcoWoods is the commercial proving ground.
• FloorForge, PaintForge and DryForge are vertical experiments.
• Runway Fuel becomes generalized infrastructure only after repeated customer evidence.

3. Find the money

Identify workflows where businesses lose money, and rank every problem by PAIN × FREQUENCY × BUDGET × URGENCY × ABILITY TO PAY × REPEATABILITY.

• lead response
• estimating
• quoting
• scheduling
• dispatch
• procurement
• labor utilization
• material waste
• change orders
• job documentation
• customer communication
• invoicing
• collections
• warranty
• quality control

4. Commercial wedge

Choose ONE vertical initially: flooring, painting, drywall, specialty contractors, field service or industrial service. The winner is the vertical where customers can be acquired cheaply and immediate financial ROI can be demonstrated.

5. Product strategy

The initial product solves a complete workflow — lead → estimate → quote → schedule → job → documentation → invoice → payment — but not every stage is built automatically.

6. Runway Fuel

Runway Fuel remains a platform hypothesis. Shared components are extracted only after at least two independent customers require similar workflows.

• identity
• organizations
• users
• permissions
• jobs
• assets
• documents
• workflow engine
• notifications
• audit logs
• integrations
• AI tools
• reporting
• billing

7. Agentic workflows

Agents are built around specific economic workflows — estimation, sales, operations, finance — each with explicit permissions and a human approval step.

8. Web intelligence

Continuously monitor competitors, vertical SaaS, ERP products, AI-native vertical SaaS, pricing, acquisitions, customer complaints, forums, trade publications, search trends and new AI capabilities. Extract unmet demand.

9. Customer research

Interview real buyers. Minimum initial target: 50 conversations. Track industry, company size, revenue, current software, workflow, pain, cost, decision maker, budget, urgency, competitors and willingness to pay.

10. Revenue experiments

Test monthly SaaS, annual SaaS, setup fee, implementation fee, usage pricing, per-user, per-job and percentage-of-value. Optimize for ARR, gross margin, retention, CAC and payback period.

11. Hard kill rule

A vertical that cannot produce meaningful commercial evidence within the validation period is frozen. A feature that does not improve revenue, conversion, retention, gross margin or utilization is not built.

12. AI discoverability / web dominance

Authoritative online assets for each winning niche: product page, industry landing page, problem guides, implementation guides, comparison pages, API and workflow documentation, case studies, ROI calculators, FAQ, structured metadata, AI-readable documentation.

13. Shared infrastructure

Share infrastructure with the other clusters only where it creates economic value: authentication, billing, observability, deployment tooling, AI model gateway, secrets management, analytics, audit logging, documentation tooling.

14. Integration with the other clusters

Integration happens through contracts, not spaghetti dependencies. Energy Intelligence produces an operational event; Runway Fuel converts it into a workflow; Physical AI executes the physical task; the result returns to Energy.

15. Weekly CEO report

Revenue, MRR, ARR, pipeline, leads, qualified opportunities, conversion, churn, retention, gross margin, customer requests, top workflow, top failure, competitive change, features killed, customers won, customers lost, next 7 days.

16. 90-day objective

50 customer conversations, 10 qualified opportunities, 3 serious design partners, 1+ paying customer. Then optimize.

Final rule

This cluster exists to make money.

• Revenue beats elegance.
• Customers beat opinions.
• Retention beats downloads.
• ROI beats features.
• Distribution beats architecture.
• A working ugly product with paying customers beats a beautiful platform with zero customers.

SELL · MEASURE · ITERATE · KILL · REPEAT