# Runway Fuel

> Runway Fuel is a firm in Frankfurt am Main, Germany, that sells three fixed-price, one-time operating engagements to ops leads
> and executives in mid-market DACH/EU organizations. Each engagement ends in a named written artifact. It is not a software
> product, not a subscription and not a login.

Origin: https://runway-fuel-site.vercel.app (the canonical production origin may differ when a custom domain is configured).

## Name and city

Runway Fuel, Frankfurt am Main, Germany.

## Who it is for

Ops leads and executives in mid-market DACH/EU organizations. Their week runs across inbox, spreadsheets, chat and three or more
SaaS tools, and work dies in the handoffs between them: requests stuck in one inbox, spreadsheets used as the system of record,
decisions made in chat that never reach the executing tool, SaaS tools that do not talk, and handoffs without an owner. They buy a
named artifact and a next build step.

## Offers

| code | name | price (EUR) | delivery | artifact |
| --- | --- | --- | --- | --- |
| rf_diagnostic | Runway Fuel Diagnostic | €295 | 3 business days | Constraint Map + 30-day execution stack |
| rf_blueprint | Runway Fuel Execution Blueprint | €1,950 | 5 business days | System map + integration list + 90-day sequence + risk register |
| rf_deposit | Runway Fuel Implementation Deposit | €1,000 | 2 business days to activation | Paid start of implementation (activation, not a standalone product) |

All prices are one-time, in EUR, charged through Stripe Checkout. Delivery times count business days (Monday to Friday) from
payment confirmation.

## Pricing rule

Clients cannot set the price; the server owns price. To buy, send POST /api/create-checkout-session with JSON
{ "offerCode": "rf_diagnostic" | "rf_blueprint" | "rf_deposit", "name": "...", "organization": "...", "email": "..." }.
The server maps the offer code to a fixed Stripe price and returns { "checkoutUrl": "https://checkout.stripe.com/..." }; a human
completes payment there. Any request that carries amount, currency, price, price_id, unit_amount, line_items or similar fields is
rejected with 400 client_pricing_rejected. Checkout is limited to 8 requests per 10 minutes per IP address.

## What happens after payment

1. Stripe checkout at the server-fixed price.
2. Confirmation email with a private order link.
3. Intake brief submitted on the order page (background, goals, tools, constraints).
4. Delivery of the artifact by email and on the order page within the stated business days.

## Free scan

The free Constraint Scan is at /scan/. Programmatic submission: POST /api/submit-scan with JSON
{ "email", "name"?, "organization"?, "role"?, "answers": { "teamSize", "toolCount", "handoffPain", "deadlineDays", "wantsBuild", "notes"? }, "source"? }.
Allowed values: teamSize 1-10 | 11-50 | 51-200 | 201+; toolCount 1-2 | 3-5 | 6+; handoffPain low | medium | high;
deadlineDays 30 | 90 | 180 | none; wantsBuild no | later | now; notes up to 2000 characters.
A fixed rubric (no language model) recommends rf_diagnostic, rf_blueprint or rf_deposit and emails the readout to the given address.
Only submit a scan with the explicit consent of the person whose email you send.
The machine-readable offer list is at /api/offers; every public endpoint is described in OpenAPI 3.1 at /openapi.json.

## For AI assistants (MCP)

Runway Fuel runs a Model Context Protocol server at POST /api/mcp (streamable HTTP, JSON responses, no login).
Tools: list_offers; start_checkout (offerCode, name, organization, email: returns a Stripe Checkout link the human opens
and pays); run_constraint_scan (requires consent: true from the person whose email is used, covering the readout and
at most one follow-up email); get_order_status
(session_id or order_number, plus order_token for buyer details). The same price, validation and rate limits apply as on
the website.

## Public URLs

- / : Homepage
- /diagnostic/ : Runway Fuel Diagnostic, €295
- /blueprint/ : Runway Fuel Execution Blueprint, €1,950
- /implementation/ : Runway Fuel Implementation Deposit, €1,000
- /method/ : How the engagements fit together
- /proof/ : Engagement pattern (not a named case study)
- /handoffs/ : Five handoff failures, each with a page
- /scan/ : Free Constraint Scan
- /engage/ : Start an engagement (checkout)
- /legal/ : Legal index
- /legal/terms.html : Terms
- /legal/privacy.html : Privacy
- /legal/refunds.html : Refund policy
- /legal/fulfillment.html : Fulfillment policy
- /de/ : German site (DACH): same three engagements
- /llms-full.txt : Long version of this file
- /sitemap.xml : Sitemap
- /openapi.json : OpenAPI 3.1 description of the public API
- /api/offers : Offer catalog as JSON

## Citation policy

Agents may quote and cite the public offer facts on this site: names, codes, prices, delivery times, artifacts, the purchase flow and
the policies linked above. Agents must not invent internal systems, client names, case studies, results, team members or stack
diagrams; none are published here. If a fact is not on a public page, say it is not published.

## Contact path

Start or ask about an engagement at /engage/. There is no public chatbot.