The entry offer

Don’t hire us for an AI transformation. Give us one workflow.

We document it, establish the baseline, build the system, launch it and operate it for 30 days. You see the actual result before deciding whether DevnTech should touch anything else.

  • From $4,500
  • About 4 weeks to launch
  • 30 days of operating support included

Why this shape

You shouldn’t have to trust an unknown company with your operations.

So we built the offer so you don’t have to. The acceptance criteria are agreed in writing before development starts, and if the system misses them, there is no implementation fee.

If it does not meet the acceptance criteria we agree before development starts, there is no implementation fee.

Not a satisfaction guarantee, which means nothing. A number, with a threshold, that we both signed at the end of week one.

We would rather lose money on the first engagement than talk a company into a twelve-month contract on the strength of a slide deck. If the pilot works, the second workflow is an easy conversation. If it does not, you found that out for a fixed, small amount.

  1. 1

    Pick one operational workflow.

  2. 2

    We document the current baseline.

  3. 3

    We agree in writing on what success looks like.

  4. 4

    DevnTech builds the first production implementation.

  5. 5

    We operate it for 30 days.

  6. 6

    You see the KPI dashboard.

  7. 7

    Only then do we discuss expanding the relationship.

Scope

What’s included

  • Workflow mapping
  • ROI baseline
  • Production implementation
  • Necessary integrations
  • Monitoring and alerting
  • KPI dashboard
  • 30 days of operating support
  • Documentation
  • Handoff option

Price

From $4,500

One workflow, end to end, including the 30 days of operating support. The exact figure depends on how many systems the workflow touches, and it is quoted in writing before anything starts. There is no retainer attached to it.

Timeline

What happens, and when

  1. Day 1

    Kickoff. We meet the people who perform the workflow today.

  2. Week 1

    Workflow mapped, baseline captured, KPI and acceptance criteria signed off.

  3. Week 2 to 3

    Build, with working software in your data reviewed at least twice a week.

  4. Week 4

    Launch into the real workflow with monitoring, safeguards and a rollback path.

  5. Days 30 to 60

    We operate it, fix what breaks, and optimize against the KPI.

  6. End of pilot

    KPI report against the baseline. You decide what happens next.

Before the pilot

We’ll map your first 3 automation opportunities

Most companies are not ready to pick a workflow on the first call, because nobody has ever costed them side by side. So the step before the pilot is a diagnostic, and for qualifying businesses it is free.

Opportunity 1

  • Current workflow, as it runs today
  • The system we would put in its place
  • Estimated implementation complexity
  • Estimated capacity impact
  • Data and access required
  • Risks and what could go wrong

Opportunity 2

  • Current workflow, as it runs today
  • The system we would put in its place
  • Estimated implementation complexity
  • Estimated capacity impact
  • Data and access required
  • Risks and what could go wrong

Opportunity 3

  • Current workflow, as it runs today
  • The system we would put in its place
  • Estimated implementation complexity
  • Estimated capacity impact
  • Data and access required
  • Risks and what could go wrong

Plus a recommended first pilot, so the call ends with a decision instead of a follow-up.

Apply

Apply for a pilot

Tell us about the workflow. If it is a fit we will say so on the first call, and if it is not we will tell you that too — including when we think you should not automate it at all.

Built for established businesses. Typically best suited to organizations with $5M+ in annual revenue and recurring internal processes.

Step 1 of 3The workflow

What would you like to improve?

Plain language is perfect. “Orders come in by email, someone types them into our ERP, then updates a spreadsheet for the weekly report.”

Questions

About the pilot

What exactly do we get at the end of the 30 days?

A production system running in your real workflow, a KPI dashboard measured against the baseline we captured before we built anything, written documentation, and a recommendation for what to do next. If you want to take it in-house from there, we hand it over.

Who needs to be involved on our side?

One person who owns the process and can make decisions about it, and access to the people who actually perform the work — usually two or three sessions of about an hour each. Without those people the workflow map is fiction, so we insist on it.

How do you pick which workflow to start with?

We look for volume, repetition, a clear owner and a measurable outcome. High volume with a stable set of rules is the best first pilot. A rare, judgement-heavy process that happens twice a month is the worst, and we will say so.

What counts as meeting the acceptance criteria?

Whatever we both signed at the end of week one, written in operational terms: processing time per item, manual touches removed, error rate, throughput. It is a number with a threshold, not a feeling about whether the project went well.

What if we want to expand after the pilot?

Then we talk about the second workflow, or about a managed systems arrangement where we operate and keep improving a set of them. Nothing about the pilot obliges you to, and we would rather you decide with a KPI report in front of you.

Do you sign NDAs?

Yes, before you send us anything sensitive. Email info@devntech.com and we will get it done the same day.

Bring us the workflow that costs you the most.

If it is a fit we will say so on the first call. If it is not, we will tell you that too — including when we think you should not automate it at all.

  • For businesses with $5M to $30M in revenue
  • No long-term commitment
  • Start with one workflow
  • Keep ownership of everything we build