How we work

Weeks, not quarters.

A repeatable four-step engagement. The same shape for a pricing model, a forecasting system, or a document workflow — what changes is the metric we're moving and the data we're moving it with.

Four steps

From problem to production.

Step 01

Identify

Map workflows, shortlist candidate decisions by feasibility and value, and pick the one or two we'd put real money behind.

Step 02

Design

Map data, workflow, and ownership. Lock the metric we're moving and the criteria for success before any code is written.

Step 03

Deploy

Build a focused MVP, instrument it, and put it in front of real users. Iterate against the metric — not against the demo.

Step 04

Adopt

Train the people in the workflow, set up internal champions, and stay on long enough that adoption survives our exit.

Operating principles

The non-negotiables.

Value 01

Metric before model.

If we can't agree on what we're moving and how we'd measure it, we don't take the work — no exceptions, no "we'll figure it out in flight".

Value 02

Build narrow, learn fast.

A small system in production beats a large one on a roadmap. The first MVP is intentionally smaller than the team would like.

Value 03

Adoption is the deliverable.

Engagement isn't done at deploy. It's done when the workflow runs without us in the room.

Value 04

Direct over decorative.

Plain language, defensible numbers, and one chart that says the thing instead of three that suggest it.

Frequently asked

Questions teams ask before signing.

How long is a typical engagement?

Discovery is 2–4 weeks. A first MVP ships in 8–12 weeks from the day data access lands. Most relationships continue past the first system, but we never sell duration up front — we sell the next decision worth changing.

Do you work with our existing data and tooling?

Yes. We adapt to your stack rather than asking you to adopt ours. If a tool is already in use and the team is fluent, that's almost always the right place to embed the new system.

Can you sign an MSA / handle procurement?

Yes. We've worked with mid-market and enterprise procurement, including DPA, SOC2 vendor reviews, and custom MSAs. Expect 1–3 weeks to clear, in parallel with discovery.

Do you build models from scratch or use foundation models?

Whichever wins on the metric. Most workflows we touch use a foundation model orchestrating retrieval and rule layers; some need a bespoke forecasting or pricing model. We don't have a religion about it.

What does pricing look like?

Engagement-led — fixed-fee phases for discovery, then a scoped MVP. We share a range on the first call once we understand the workflow. We don't publish a rate card; the work is too varied to commodify.

Start with a discovery session.

We'd rather scope a focused engagement around a single decision than promise a transformation. The second use case finds itself.

Book a 45-minute call → contact@eca-labs.com