What clients ask before they commit to a first engagement.
- What is in scope for a first engagement?
- One workflow, chosen on volume and repeatability: support triage, sales follow-up, knowledge retrieval, back-office automation, a voice agent or an AI readiness review. Scope is fixed before we start, in writing, so you know what arrives. Anything discovered along the way is quoted separately rather than absorbed silently.
- What does Artellis deliberately not do?
- We do not sell licences, resell software, or run a rebadged offshore team. We also do not build anything that acts on customers or money without a person approving it. Output from Artellis work is decision support: your team reviews, tests and approves it before operational use.
- Who owns the tool once it is built?
- You do. Accounts, credentials, code and data sit in your name from day one, and the handover includes documentation written so another developer could take it over. There is no lock-in and no monthly fee needed just to keep the workflow running.
- How is the work priced?
- Fixed-scope engagements rather than day rates: a discovery week, a prototype, or a shipped build. Price depends on the workflow, the systems it touches and how much of the running you want to own. Ella on this page can size it roughly; Richie confirms a firm number on a call.
- What happens after handover?
- Your team runs it. You get the documentation, the training session, and a short written record of what the workflow does and where the human approval sits. Ongoing support is optional and priced separately, never assumed as part of the build.
- Can we start with something small to test you out?
- Yes, and most clients do. A discovery week ends with a working prototype on your own data and an honest view of whether the rest is worth building. If the answer is no, you are told so, and the week still leaves you with something usable.