Service levels
Three levels of scope, priced after discovery
These are not plans you buy from a page. They describe how much of the customer journey the system covers and how much integration work it involves, so you can tell roughly where your situation sits before the first conversation.
How the commercial model works
A service engagement, not a subscription to software. Three components, and we are explicit about which apply to you before anything is agreed.
One-time setup and implementation
Design, build, integration, testing, and launch. Quoted once, against the written scope produced at the end of solution design.
Ongoing support, where it applies
Monthly monitoring, adjustment, and optimisation for systems that need it. Optional on smaller engagements; effectively necessary on larger ones, and we will say which yours is.
Third-party costs, billed to you directly
AI model usage, telephony, messaging platforms, hosting, and any software subscriptions run on your own accounts and are paid by you at cost. We never mark them up, because we never touch them.
Service levels
Simple
One clear gap, closed properly.
- Suited to
- A business with a single obvious problem — usually enquiries arriving outside working hours with nobody to answer them.
- Typical scope
- One or two channels, a text agent, structured capture into one destination, and basic notification routing.
- Included capabilities
- Text agent on one or two channels
- Knowledge base built from your services and policies
- Structured capture into a CRM, sheet, or shared inbox
- Notification routing to a named person
- Turkish and English, or another pair you need
- Testing, launch, and handover documentation
- Customisation
- Standard conversation flows adapted to your content. Qualification is a small, fixed rule set.
- Integration complexity
- One or two, using supported connectors where they exist.
- Support
- Optional monthly support. At this scope it is not a requirement.
Advanced
Our usual starting pointThe journey, end to end.
- Suited to
- A business losing customers at more than one point: enquiries across several channels, no reliable capture, and follow-up that happens when someone has time.
- Typical scope
- Multiple channels including voice where appropriate, full qualification and routing, CRM automation, and follow-up sequences.
- Included capabilities
- Everything in Simple, across all your active channels
- Voice agent for missed and out-of-hours calls
- Qualification and classification against your own criteria
- CRM setup or cleanup, with event-driven stage changes
- Follow-up and appointment-reminder sequences
- Retention and re-engagement workflows
- Reporting on volume, response time, and stage conversion
- Customisation
- Conversation flows, qualification logic, routing, and follow-up intervals all designed against your process.
- Integration complexity
- Several, including custom connections where a supported one does not exist.
- Support
- Monthly support included in the scope. Systems this size need someone watching them.
Ultra-Advanced
Operations that span systems and locations.
- Suited to
- A business with multiple locations, teams, or brands, or one whose process spans systems that do not talk to each other and where the integration work is the substance of the engagement.
- Typical scope
- Everything in Advanced, plus deep internal process automation, complex or legacy integrations, and per-location or per-team logic.
- Included capabilities
- Everything in Advanced
- Multi-location, multi-team, or multi-brand routing
- Internal process automation beyond the customer journey
- Custom integrations with internal or legacy systems
- Document and record generation from live data
- Approval steps and escalation paths designed with you
- Reporting split by location, team, or service line
- Customisation
- Designed from your processes rather than adapted from a pattern. Expect the design phase itself to be substantial.
- Integration complexity
- Complex, including systems with no public API where a workable route exists — assessed honestly during discovery.
- Support
- Ongoing support and a scheduled optimisation cycle are part of the engagement.
Third-party costs are separate
The systems we build run on services that charge for what they use. Those accounts are yours, the bills come to you directly, and we do not add a margin to them.
- AI model usage, charged by volume of conversation
- Telephony — phone numbers, inbound minutes, and call handling for voice agents
- Messaging platform fees, where the platform charges for business messaging
- Hosting and domain costs for websites and touchpoints we build
- Subscriptions for any CRM, automation, or scheduling tool the design depends on
During solution design we estimate these based on your enquiry volume, so the running cost is visible before you commit rather than after the first invoice.
Why there are no prices on this page
A figure printed here would be either meaningless or misleading. Two businesses asking for 'an AI agent' can differ by an order of magnitude in scope: one needs a website chat answering eight questions, the other needs voice, three channels, a CRM migration, and an integration with a booking system that has no public API. We quote against a written scope, after discovery, so the number means something. If your budget has a hard ceiling, say so in the first conversation — it is a design constraint like any other, and it is better to design within it than to quote past it.
Commercial questions
What people ask about cost and commitment
The questions that come up before the first consultation.
Can you give a rough range before discovery?
In the first consultation, once we know which channels and systems are involved, we can usually indicate which service level fits and what would drive the cost up or down. A firm number comes with the written scope.
Is the first consultation really free?
Yes, and there is no obligation to proceed. Its purpose is to establish whether we can help. If automation is not the right answer for your situation, we would rather say so than scope something.
Do I have to take ongoing support?
On a Simple engagement, no — some businesses run it themselves after handover. On Advanced and above it is part of the scope, because a system that spans several channels and integrations will drift, and unmonitored drift is how a customer discovers your agent is answering wrongly.
Who owns the accounts and the data?
You do. Integrations are connected using credentials issued from your own accounts, customer data stays in systems you control, and nothing is created under a Relnivo account. If we stopped working together, the system keeps running.
What happens if the scope changes mid-engagement?
We re-scope and re-quote the addition rather than absorbing it silently or letting it stretch the timeline without explanation. Changes that reduce scope work the same way.
Do you charge for the discovery and design phase?
The first consultation is free. Where discovery and journey mapping are substantial — typically at the Ultra-Advanced level — that phase may be quoted separately, and we tell you before it starts, not after.