People ask what happens after they send a message. The answer is short, and it is the same for a small business that wants a website as for an enterprise that wants AI beside its ERP. Only the size of each step changes.
There is no sales sequence. A person reads what you wrote.
01Before any work: four steps
- You write. A few lines on your organisation, the problem and where your data lives is plenty.
- We read it properly. A person reads every message and replies personally.
- We talk. A conversation about what you need, and an honest view on whether we can do it.
- A clear next step. If there is a fit, a written scope. If there is not, we say so.
02The work itself: four stages
- Listen. We start with the problem in your words, and learn how the work really runs and what a good outcome looks like.
- Scope. We agree what will be built, what it must do and how we will know it works, before anything is built.
- Build. We design and build in stages you can see, test and question. Enterprise systems are deployed on your infrastructure.
- Hand over. We make sure your team can run, trust and extend what was built.
03What you know before you commit
- What will be built
- What it will cost
- What it must do to count as working
- What you will own at the end
You see the scope and the price before any work starts.
04What we need from you
- One person who can answer questions and make decisions
- Access to the people who do the work the system will touch
- For data projects, a sample of real data, handled as you require
- Honest feedback at each stage
05After launch
We keep it working. Websites and apps are maintained; enterprise systems are handed over with the knowledge your team needs to run them, and support continues for as long as you want it.
06If we are not the right fit
Some work is better done by a different kind of company: a consumer app sold by subscription, engineers supplied by the hour, a programme that needs a thousand people. Where that is so, the first reply says it.
In short
- A person reads every message and replies personally.
- The work runs in four stages: listen, scope, build, hand over.
- Scope and price are agreed in writing before work starts.
- After launch the work is maintained, and enterprise systems are handed to your team.
Questions
How do I start?
Write to hello@quantumbeetle.ai and describe the problem in your own words.
Do I need a detailed brief?
No. A few lines is enough to begin. Turning the problem into a written scope is part of our work.
Will you need our data to give a quote?
No. We never need your data to start a conversation. If a project needs it, we agree how it will be handled first.
Do you work on site?
Remotely or on site, as the work needs. Enterprise systems run on the client's own infrastructure.
Sounds like your problem?
Tell us about it. We'll say honestly whether the swarm can help, and what it would take.
Read next
- What is Quantum Beetle?The company
- What "the swarm" means: one brain, many mindsThe idea
- How Quantum Beetle prices its workPricing
- Quantum Beetle's products: MIDAS, ARGUS, ATLAS and MNEMOSThe products
- Who Quantum Beetle is for, and who it is not forWho it is for
- Why Quantum Beetle runs AI on your own serversSovereign by design