Bot Resources

Four Phases. Clear Gates. No Surprises.

Each phase answers one question. Each phase is non-committing - neither you nor us are obligated to continue. Each step earns the next.

0

Scoping

"Are we a good fit to work together?"

2 weeks, 2-3 meetings max

What Happens

  • First contact, discuss the envisioned use case
  • We challenge together: Is this the right problem? Is it automatable?
  • We help specify the use case if needed
  • Mutual evaluation: Can we work together?

Your Team

Domain experts (essential), decision-maker

Bot Resources

Senior architect or flow engineer

Deliverables

Specified use caseGo/no-go decisionIf go: priced proposal for POC

What We Don't Do

  • 3 months of free work to respond to an RFP
  • 50-page specs without talking to domain experts

At the Gate

Good fit, clear use case

We move forward with a priced proposal for POC

Use case doesn't fit, but we click

We explore other use cases together — sometimes the best ideas emerge from conversation

Rubber stamping risk

If a 'decision support' tool would just get blindly validated, we need to rethink the use case entirely

Cultural misfit

Better to know now. We part ways respectfully.

1

POC

Proof of Concept

"Can this task be done by an agentic system?"

4-6 weeks total

What Happens

  • We build a real prototype (not a script, not a basic chatbot)
  • Fast deployment for users to test
  • Users test, break it, give feedback
  • We iterate directly with them
  • At the end: users know if it's useful to them
If IT integration is required during POC (SSO, VPN access, data connectors…), this is scoped and priced separately as an add-on.

Your Team

Domain experts / end users (direct access)

Bot Resources

1 flow engineer + 1 architect + coding agents

Deliverables

Working POC systemDocumented user feedbackAnalysis: works / doesn't work (and why)If it works: specs and budget for POV

At the Gate

It works — users find it useful

We spec out the POV with clear targets and move forward

Model limitations — not yet

We document what's missing. Can set up a technical watch to revisit when models evolve.

2

POV

Proof of Value

"Can we reach the performance level needed to create value?"

1-3 months

What Happens

  • Extend coverage (more cases, more scenarios)
  • Continuous iterations with users
  • Performance improvements
  • Domain-specific benchmarks for model selection (if needed)
  • API cost optimization (if needed)
  • Agent architecture refinement

Your Team

Domain experts + IT (for integration/deployment)

Bot Resources

1-2 flow engineers + 1 architect + coding agents

Deliverables

MVP delivering real valueWorking system per agreed specsTechnical documentationPerformance metrics

At the Gate

Targets met

System works per specs — delivery accepted, ready for industrialization

More effort needed than expected

We discuss openly. You decide: extend the budget or adjust scope.

Model capability gap

We pause, set up monitoring for model evolution. Technical watch available.

3

Industrialization

"How do we make this robust, integrated, and sustainable?"

Ongoing

What Happens

  • Robustness reinforcement
  • Deep integration with client systems
  • Monitoring setup
  • Knowledge transfer to client teams
  • Evolutive maintenance (new features, adjustments, model updates)

Your Team

IT (owns integration), business (owns usage)

Bot Resources

Team available for support

Deliverables

Robust production systemComplete documentationAutonomous client teamsOngoing support
Billing: POC/POV: fixed price per project. Industrialization: fixed price per feature or time-based with annual commitment.

Ongoing Relationship

Your teams become autonomous

Knowledge transfer complete. You own the system.

Continuous evolution

New features, model updates, scope extensions — we grow with your needs

Ready to start?

A first conversation costs nothing but time. Let's see if we're a good fit.

Let's Talk About Your Project