We reply
A person reads the message, and that person answers you. No autoresponder.
If it makes sense, we book a 30-minute call. If it does not, we say so.
A person reads the message, and that person answers you. No autoresponder.
You show us the process as it is today. We ask the awkward questions: who uses it, how many times a day, what happens when it goes wrong.
Where we would start, on what timeline, in what order of magnitude of cost. If you say no, that is where it ends.
what to writeYou do not need a specification. The process that weighs on you, where it gets stuck and who uses it every day is enough: we get to the rest together on the call.
It depends on three things: how many systems need connecting, how much volume goes through and how much human review is needed. Before the call any figure would be made up, but the path is this: discovery ends with an estimate, and each phase after that is decided on the numbers from the one before, without committing blind to the whole project. The order of magnitude comes right after the call, which is free.
No. Working out which data actually matters is half the job, and that half is ours.
No. AI goes into the ERP, the CRM and the website you already have: we know TeamSystem and SAP Business One, and for anything else an API or an export is enough. If a piece does need rebuilding we tell you beforehand, not halfway through.
We have been writing software since 2010. AI is one more tool, not the only one we have.