We have no list price, we have a scope list.
The same job takes different effort at two companies. The number of pages and channels, the systems to connect and the content needed all change the work. So we do not put a figure on this page; we put down what the figure depends on.
The call takes 30 minutes and needs no preparation.
The price has two lines.A third one does not appear.
The proposal is itemised and arrives with the discovery report. If scope grows during the build we talk first and write second; no line is added by surprise.
Build
Discovery, the demo, design, software, connecting the systems and training the team. Everything up to going live sits in this line.
Operation
Maintaining the running system, updates, measurement, reporting and support. If agreed, SEO, GEO and AEO work sits here too. We do not assume the work ends when the build does.
The discovery report comes with the proposal: what we will build, how long it takes and what gets measured are all in writing.
Three sample scopes.Yours may sit outside all of them.
Starter
Start with one assistant on a single channel.
Teams automating for the first time
- One AI assistant, on WhatsApp or the website
- Answering common questions and taking appointments
- Basic integration with your existing systems
- Build and team training
- Monthly maintenance and updates
Growth
Connect several channels and workflows to one system.
Teams with rising demand and more than one inbound channel
- Multi-channel assistant across WhatsApp, Instagram and web
- Optional voice assistant
- Workflow automation with n8n, Make or Zapier
- CRM integration and request tracking
- Prioritised support
- Continuous improvement and measurement tracking
Enterprise
A system built around your business and connected to every program you use.
Organisations that need a sector platform and custom software
- Sector-specific platform build
- Custom software built from scratch
- Multi-system and API integration
- Dedicated service level and assigned team
- Advanced reporting and data analysis
- Enterprise data handling under GDPR and KVKK
The packages are examples, not a fixed menu. If the work discovery turns up does not fit any of them exactly, we write the proposal for that work.
Four things move the figure most.You see each of them in the proposal.
We work through all four on the discovery call, so you can see line by line why the proposal says what it says.
Scope
A one-page site and a multilingual site with a management panel are not the same job. Nor are a single WhatsApp line and four channels running together; each channel brings its own testing.
Integration depth
Connecting to a CRM with a ready-made integration is not the same as connecting to a system you wrote yourself. How many systems, and in which direction we write, drives the length of the build.
Volume
Forty requests a day and four thousand are not served by the same infrastructure. Volume changes both the build decisions and the monthly running cost.
Approval layer
Where human approval sits is a design decision. Builds that need an approval queue, separated permissions and an audit log take more work.
The package changes,these do not.
- Discovery report: where the problem is, the fix we propose and the measurement plan, in writing.
- Audit log: what the system did is recorded and can be read afterwards.
- Human approval: the step that needs judgement stays with a person, with a finished draft in front of them.
- Ownership: the system and the data stay yours, and the source code is handed over.
- Data processing agreement: part of the build, not a line added later.
What the price does not include.We say this up front.
- We do not resell licences. Subscriptions for the tools used are opened in your name and billed to you; we take no cut in between.
- Ad budget does not pass through our account. Meta and Google spend comes straight out of yours.
- We do not write a proposal for work that is not worth building. If discovery shows it is not, we tell you.
Pricing Frequently asked questions
Because scope differs from company to company, a single figure would be either always too high or always too low. Instead we write down what drives the price, and the proposal arrives itemised with the discovery report.
Discovery takes about a week. After it you receive, in writing, where the problem is, the fix we propose and the measurement plan; the proposal sits inside that report.
It depends on the scope. On an automation build the first live workflow opens within 4-8 weeks; your own timeline is written into the discovery report.
Not for the scope written into the proposal. If you want to widen the scope during the build we talk first and write second; no line is added without your approval.
You can. The system is handed over and your own team maintains it; the source code and the audit log are yours in any case. Keeping the measurement going becomes yours from that point too.
Not in the usual sense, because a build is not a product you switch on. Instead there is the discovery week and the demo, so you see together whether the work is worth doing. If it is not, we are the ones who tell you.
Websites and mobile apps, Meta and Google ads, workflow automation, chat and voice assistants. Client records, email marketing, SEO, GEO and AEO work, branding and print design are included too. If a request is not on the list, we research it first.
We write the proposal after we have found the problem together
In a thirty-minute call we listen to how you work and talk through where time and customers are slipping away. If you do not need a digital fix, we will tell you that too.
30 minutes · no preparation needed
