Radical transparency
Why you might not want to hire DevnTech
Most agency websites are a list of reasons to say yes. This is the other list. If two or three of these describe your situation, we would rather you knew now than after a call — and we will tell you the same thing on the call anyway.
We’re probably not a fit if
Seven situations where we would tell you no
You’re looking for a one-off chatbot demo.
A demo is a one-week project with no owner and no measurable outcome. Somebody will build you one cheaply, and it will sit unused. We would rather you spent that money on a workflow that has a number attached to it.
Nobody inside the business owns the underlying process.
Without an internal owner, there is nobody to answer the questions the build surfaces, nobody to approve a process change, and nobody to keep the improvement going after we hand over the KPI report.
You can’t give us access to the people who actually perform the workflow.
The workflow map is only accurate if it comes from the people doing the work. Built from a manager’s description, it will miss the exceptions — and the exceptions are where automation projects fail.
There’s no measurable reason to automate it.
If we cannot state the number we are trying to move, we cannot tell whether it worked, and neither can you. That makes it a technology purchase rather than an operational improvement.
You need a large consulting presentation rather than an implementation.
We are an implementation company. If you need a strategy deck and a steering committee, there are excellent firms for that, and we are not one of them.
You expect AI to fix a broken process without changing the process.
Automating a broken process makes it produce wrong results faster and at greater scale. Where the process itself is the problem, we will say so before building anything.
You’re not prepared to measure the result.
Measurement is not overhead we add to justify our fee. It is the only way to know whether to expand, adjust or stop — and a client who will not measure cannot make that decision.
On the other hand
What a good fit looks like
If most of these are true, the first conversation is usually short and productive.
- The workflow happens often — many times a week, ideally many times a day.
- The rules are stable enough to write down, even if nobody has written them down yet.
- One person owns the process and can make decisions about changing it.
- You can put a number on what it costs today, or you are willing to measure one.
- You want the system operated after launch, not handed over and forgotten.
- You would rather hear "do not automate this" than be sold something.
If you read that and thought “that’s us”, let’s talk.
Describe the process. If we are the wrong choice we will say so on the first call, and point you at what we think you actually need.
- For businesses with $5M to $30M in revenue
- No long-term commitment
- Start with one workflow
- Keep ownership of everything we build