Prove the value.
Then shape the scale.

A focused six-week pilot gives us the evidence to build the right solution—and the right commercial agreement—for your business.

Scope a pilot

Six-week pilot

Fixed fee, scoped together.

One priority workflow. A clear baseline. A working solution tested with the people who will use it.

  • Workflow discovery and agreed success measures
  • Build, integration, and evaluation within the agreed scope
  • A controlled trial with a defined group of users
  • An outcomes review and recommendation for what comes next

We agree on scope, deliverables, fees, and any third-party costs before kickoff. The six-week delivery window starts when agreed access and prerequisites are ready.

See the six-week plan

Enterprise partnership

Custom pricing.

A commercial model built around the solution, deployment requirements, and level of ongoing ownership.

  • Project-based delivery for a defined implementation
  • Ongoing support and improvement for a managed workflow
  • Embedded engineering capacity for a broader roadmap

We use the pilot findings to scope a separate enterprise proposal. Continuing beyond the pilot is a deliberate decision, with new terms agreed before work expands.

What shapes the proposal

Start with the opportunity.
Align before we build.

The first conversation is about your business: where work gets stuck, who owns it, and what improvement would be worth.

Identify a workflow worth changing.

Review the volume, cost, quality issues, and handoffs. Choose a bounded opportunity with an owner, accessible data, and a measurable outcome.

Agree on the pilot.

Document the scope, fee, deliverables, success criteria, responsibilities, and dependencies in a pilot statement of work. Align on confidentiality, data handling, security review, and access before delivery begins.

Six weeks.
A decision grounded
in real work.

The pilot is designed to answer a practical question: does this workflow justify a broader investment?

An indicative delivery plan, tailored in the pilot scope. Integration complexity and client dependencies may change the sequence.

  1. Week 1

    Establish the baseline.

    Map the workflow with your team. Confirm the starting metrics, representative data, users, and acceptance criteria.

  2. Week 2

    Design the smallest useful solution.

    Choose the integration path, human review points, and evaluation approach. Resolve the riskiest assumptions early.

  3. Weeks 3–4

    Build and test in context.

    Develop the scoped workflow, connect the agreed systems, and test quality, failure cases, and usability with your team.

  4. Week 5

    Put it into controlled use.

    Run with the agreed pilot group and safeguards. Observe adoption, exceptions, and performance in the actual workflow.

  5. Week 6

    Evaluate the return. Identify the next move.

    Compare results with the baseline. Assess operating costs and readiness. Recommend whether to expand, refine, or stop—and define the shape of a production solution.

The solution shapes
the contract.

A single internal workflow and a business-critical platform need different delivery teams, commitments, and economics.

What we scope together

Workflow & integrations
Number of processes, systems, data sources, and the depth of integration.
Deployment & controls
Hosting requirements, data boundaries, access controls, security review, and human oversight.
Usage & ongoing work
Expected volume, model and infrastructure costs, support coverage, and the improvement roadmap.
Delivery & adoption
Milestones, stakeholders, training, operating ownership, and the capacity needed to deliver.

Then agree on the enterprise terms.

We work with your business, procurement, security, and legal teams on the applicable services agreement and statement of work: scope and acceptance, fees and billing, data and IP arrangements, service expectations, change requests, and renewal or exit terms.

The proposal makes implementation costs, recurring fees, and third-party usage costs explicit. The signed agreement defines the commitments.

Before we begin.

Do we need to know exactly what to build?

No. Bring a costly or frustrating workflow and a person who understands it. We’ll work together to identify a pilot that can test both technical feasibility and business value.

What do you need from our team?

A business sponsor, a workflow owner, representative users, and the agreed access to systems and data. We define those responsibilities and any security or procurement prerequisites before kickoff.

What happens if the pilot doesn’t justify scaling?

The final review should make that clear. We discuss whether a smaller iteration is worthwhile or whether to stop. An enterprise rollout is a separate decision, not an automatic next step.

Who owns the solution, and who runs it?

We agree on deliverable ownership, licensing, data use, and operating responsibilities in the contract. The right arrangement depends on whether your team will own operations or wants ongoing support from Automorphism.

Are model and infrastructure costs included?

The proposal specifies what is included, what is billed separately, and any usage assumptions or limits. We discuss these costs before work begins and revisit them when the deployment scope changes.

Start with one
valuable problem.

Tell us the workflow, the friction, and the outcome you want.
We’ll work out whether a six-week pilot is the right next step.