Pricing & Onboarding

We are a small operator — can we realistically afford a proper BSS without paying for enterprise features we will never use?

This is one of the most common questions we get, and the honest answer is: it depends on your volumes and which modules you actually need. BlueRockTEL's pricing is modular — you pay for what you use, not for the full platform if you only need part of it.

A smaller operator starting with billing alone pays for billing. They are not subsidising a Deployments module they have not adopted yet. The subscription scales with your customer volume and the modules you activate, which means the cost structure is closer to your actual operational footprint than enterprise BSS pricing typically is.

The more useful question is not "can I afford this?" but "what is it costing me not to have this?" — in unbilled revenue, staff time, and invoicing errors. To get a concrete number, request a demo and we will discuss pricing in the context of your actual volumes.

All our billing history is in our current system — how do we move it without losing data or breaking our operations?

Data migration is handled as a structured project, not a one-time data dump. Here is how it works in practice:

1. We provide specifications for the export format we need from your current system
2. You export the data; we review it for completeness and quality before importing anything
3. Data is imported, mapped, and validated in BlueRockTEL — you review the results
4. You run both systems in parallel for one full billing cycle to confirm the outputs match
5. Only after that parallel validation do you cut over fully to BlueRockTEL

The parallel run is the safeguard. No billing cycle is disrupted because you are running your current system alongside BlueRockTEL until you have confirmed everything works correctly. We have migrated customers from proprietary billing software, shared spreadsheet environments, and generic ERP systems — the methodology is established and tested.

We went through a painful software implementation once and we are not in a hurry to repeat it — how is BlueRockTEL's onboarding different?

The most common cause of painful implementations is a vendor who hands over a licence and leaves the configuration to the customer's team. BlueRockTEL's onboarding is the opposite: it is a project managed by our team, with defined milestones, sign-offs at each stage, and dedicated go-live support.

What this looks like concretely:

• We map your services, tariff plans, and billing rules to the platform — you do not need to figure out the configuration yourself
• We manage the data migration with you, not just give you an import template
• Training is conducted live with your team, tailored to their roles
• The go-live billing cycle is supported directly by our team

We also do a parallel run before you cut over, which means you have confirmed the system works for your data before you depend on it. If something is wrong during the parallel run, it is caught and fixed before it affects a real customer invoice.

We have no IT department — who actually does the technical setup?

Our team handles the technical setup. The integrations that require technical work — connecting to your CDR source, configuring SEPA file transmission, setting up the customer portal, building API connections to your other tools — are all scoped and executed by BlueRockTEL during the onboarding project.

You need a point of contact who can answer business questions (what are your tariff plans? what are your billing rules? who are your carriers?) and who can coordinate access to your current systems. You do not need an IT team to run the implementation.

Once the platform is live, day-to-day operations — running billing cycles, managing tickets, processing payments — require no technical knowledge. The platform is designed to be operated by back-office staff, not system administrators.

How disruptive is the switch? We cannot afford to mess up a billing cycle.

The parallel run approach is specifically designed to eliminate this risk. Before you switch fully to BlueRockTEL:

• You run a complete billing cycle in BlueRockTEL alongside your current system
• You compare the outputs: invoices, totals, customer records
• Any discrepancy is investigated and resolved before the cutover

Your current system remains live and operational throughout this period. You do not cut over until you have confirmed — with real data, for a real billing cycle — that BlueRockTEL produces the correct outputs. There is no leap of faith; there is a structured validation before any dependency is created.

What exactly are we committing to, and for how long?

BlueRockTEL subscriptions typically have a 12-month initial commitment. This is straightforward: onboarding requires investment from both sides, and a 12-month period is the minimum for that investment to make sense for either party.

After the initial period, the contract typically moves to annual or monthly renewal terms. The specific commitment structure is discussed openly during the commercial process — there are no buried auto-renewal clauses or exit penalties that we spring on you later.

The things worth understanding before signing:

• What the notice period is for cancellation
• What happens to your data if you leave (see the question below)
• Whether there are volume-based pricing steps that could affect your cost as you grow

We are happy to walk through these details before you sign anything.

What is actually included in onboarding versus what costs extra?

Standard onboarding includes: scoping and platform configuration, data migration, integration setup for your CDR source and payment providers, team training, the parallel run, and go-live support during your first live billing cycle.

What may be scoped separately: complex custom integrations with proprietary systems, bespoke development work for non-standard billing rules, or very large-scale data migrations from heavily customised legacy platforms.

We scope these distinctions explicitly before you sign. You will not discover mid-implementation that something you expected to be included is billed separately.

Our business model is evolving — what if we need to change things six months in?

The platform is configurable, not hard-coded. Tariff plans, billing rules, service types, dunning sequences, SLA policies, invoice templates — these are all managed through configuration rather than code changes. Your team can make most adjustments independently once you have been trained; more complex changes go through our support team.

Adding a new service type, changing your pricing structure, or adding a new carrier are not implementation projects — they are configuration tasks. The platform is designed for operators whose portfolios evolve, because that is the normal reality of the industry.

We want to start with one module — will the cost escalate when we add more?

Each module you add is priced incrementally, based on its specific scope. The cost does not reset or compound in a punishing way when you expand. If you started on billing and want to add the helpdesk eighteen months later, you are adding the helpdesk cost — not repricing the whole platform.

We review pricing with our customers regularly as their usage and scope evolve. The goal is that pricing remains proportional to the value you are getting, not that we lock you into a structure that becomes expensive as you grow into the platform.

Who do we call when something goes wrong after we go live?

After onboarding, you have access to BlueRockTEL's support team for platform questions and issues. The contact method and response time commitments are specified in your service agreement.

For strategic questions — how to handle a new service type, how to structure a billing change, whether a planned operational change is feasible in the platform — your account manager is the right contact. We do not consider our relationship with customers to be over after the go-live billing cycle.

Some context worth knowing: we have operators who have been with us since 2012. That longevity is only possible if the ongoing relationship works, not just the initial sale.

How do we know the ROI figures are real and not just marketing?

We do not publish ROI figures, because they vary significantly by operator and by where you are starting from. What we can do is help you build your own calculation during the demo, based on your actual numbers:

• How many hours per month does your team currently spend on billing?
• What is your current DSO (days to collect after invoicing)?
• Can you estimate how much revenue you might be losing to unbilled or incorrectly billed usage?

These are questions you can answer from your own data. The demo is the right place to work through them together, because the result is a number that means something to your business — not a generic case study about a different operator in a different context.

What happens to our data and operations if we ever decide to leave?

You own your data. If you leave BlueRockTEL:

• You receive a complete export of all your data — customers, invoices, CDR records, tickets — in standard, portable formats
• The export is provided at contract termination, not withheld as leverage
• Your data is retained for a defined period after termination and then securely deleted
• We assist with the transition to your new system during the notice period

This is not a favour — it is a contractual right built into our service agreement. We mention it explicitly because some vendors in this space do make exit difficult, and we think it is worth being clear that we do not.