Steepworks Cloud and Managed Pricing

Start

Every partnership starts with a paid session.

Before any build is priced, we agree on a plan in Steepworks. Business leaders, Builders, and agents work from the same record. The Validation Sprint fee is credited in full toward a Project Build started within 60 days.

See how it works

Discovery Session

Discuss the Project, clarify the first useful outcome, and decide whether validation or a direct Build proposal should come next.

$100 once

Start and book Discovery

Validation Sprint

Validate the concept, first workflow, risks, and build direction before choosing ongoing capacity. The full fee is credited toward your Project Build when you proceed within 60 days.

$1,000 once

Start Validation Sprint

Not ready for a paid session? Book a free 15-minute call first.

Project Builds

Three builds. One direction.

Each build starts with a valuable problem and a clear definition of success. Your proposal sets the scope, milestones, acceptance evidence, and initial payment for the project you agree to fund.

Make business data usable

Data Foundation

A governed data substrate for the business: internal-system connections, ingestion and normalization, connected to AI infrastructure.

From $3,500

Canonical domain model with rules and permissions
Internal-system connections with ingestion and normalization
Provenance and review for imported records
Connected to AI infrastructure from day one

Put one domain into software

Domain Application

Everything in Data Foundation, plus one production application for a defined business domain.

From $7,500

Data Foundation included
One production application for a defined business domain
Roles, permissions, and workflows
Deployment and release management

Unify a portfolio of applications

Domain Platform

Multiple connected domain applications sharing data, identity, integrations, and infrastructure.

From $15,000

Multiple connected domain applications
Shared data, identity, and integrations
Reusable capability modules
Portfolio governance and operations

Changed requirements, delayed inputs, or third-party dependencies are assessed and approved before work continues beyond the accepted estimate. Every engagement includes the shared Workspace where scope, time, decisions, and approvals stay visible.

Platform subscription

Continuous operations, active Projects, and Service Blocks.

After the build, your platform subscription covers continuous operations and continued change: it sets how many Projects can be active at once and how much delivery capacity each month includes. Capacity is a soft cap, not a meter: we tell you before you reach it, and work never stops mid-outcome.

Starter

One active Project with one Service Block of monthly capacity.

$500/mo

Active Projects: 1
Service Blocks: 1
Included capacity: 5 hours, soft cap

Growth

Three active Projects with two Service Blocks of monthly capacity.

$1,000/mo

Active Projects: 3
Service Blocks: 2
Included capacity: 10 hours, soft cap

Scale

Up to eight active Projects; price and blocks agreed per customer, from $2,000 and three Service Blocks.

From $2,000/mo

Active Projects: Up to 8
Service Blocks: 3+
Included capacity: 15+ hours, soft cap

What counts as an active Project?

A Project being worked right now. Draft, paused, and completed Projects never consume a slot, and you can prepare the next Project while the current one runs.

What is a Service Block?

A unit of included delivery capacity, sized at five hours of Steepworks attention. It is a soft cap: your Billing page shows capacity used the way it shows model usage, we warn you as you approach it, and an additional block is $500 when you want more. You buy outcomes and a running platform, never hours; time is never a hard stop and never how anyone here is paid.

Usage is funded before activation

Model usage and the infrastructure running your application are shown separately — never hidden inside blocks or plans. An agreed estimate is paid before usage or infrastructure is activated, then reconciled to itemized actuals.

Usage and infrastructure

Funded first. Reconciled to actuals.

Before we activate model usage or application infrastructure, we invoice an agreed estimate and service begins only after payment. That funded amount covers usage as it occurs. Each billing period, itemized actuals are reconciled against it: unused funds carry forward and any difference is invoiced in arrears. Additional usage or infrastructure is not enabled until the Account is funded again. For servers, databases, storage, and related services, you see the resource type and capacity, actual provider cost, agreed markup, and resulting charge without exposing our provider account details.

Aligned outcomes

Pay for work that works.

When your application can measure a valuable business result, part of our price can attach to that result. We share the upside only when the agreed outcome qualifies.

See how alignment works

Defined before work begins

The objective, qualifying event, attribution, rate, measurement window, and cap are agreed in your engagement.

Measured by the application

The application record is the evidence. If the platform cannot measure a result reliably, it does not become an outcome term.

Shared upside, not a hidden floor

No outcome fee is due when the result does not qualify. The platform subscription remains the operating floor.

Start at the right layer

Scope the first useful application together.

Start with Discovery Book 15 minutes

Choose how you work with Steepworks.