Q B A T I C
Implementation team at work

What QBatic does alongside the licence
to make sure the platform actually lands

Services

What we do

QBaticEPM3 is a working platform, not a self-serve sign-up. Heavy-industry portfolios don't migrate themselves, sectors don't configure themselves, integrations don't write themselves. We do that work alongside the licence.

The platform is sold as a software licence. Services are billed separately, scoped to what the customer actually needs, and delivered by our own implementation team. None of them are mandatory. Some customers do everything in-house and that's fine. Most take at least the implementation engagement, because moving an existing portfolio onto a new platform is the part that benefits most from someone who has done it before.

Services are quoted, scoped and signed before any work is invoiced. There are no surprise hours.

FAMILY 01
01

Implementation

Get the platform live on your data. Migration from existing systems, sector configuration, initial user training.

FAMILY 02
02

Extension

Connect, customise and scale. Integrations to your wider stack, custom develoEPMnt, dedicated single-tenant hosting where needed.

FAMILY 03
03

Operations

Keep the platform working as the business changes. Refresher training, certification, support tiers, annual health-checks.

FAMILY 04
04

Advisory

Strategic services beyond the licence. Knowledge-loss diagnostic before implementation, cost benchmarking once you're live.

Implementation team configuring the platform on customer data

Most of the value of an enterprise platform shows up in the configuration, the migration and the training. Not in the licence file.

The work in detail

What each engagement actually involves.

Every customer's situation is a bit different, but most of what we do falls into three repeatable groups of work. The lists below cover what's typically in scope, not the only things possible.

PILLAR 01
3
Services in this family

Implementation

The first engagement most customers take. We move the existing portfolio onto the platform, configure it for the primary line of business, and train the initial user group through to the point of self-sufficiency.

  • Data migration from spreadsheets, legacy estimating tools, and accounting systems
  • Sector pack configuration matching the primary business
  • User accounts, permissions, currencies and regional setup
  • Hands-on training for the initial user group
  • Hand-over to internal champions and post-go-live support window
PILLAR 02
3
Services in this family

Extension

Almost every customer needs the platform to talk to something else in their stack. Some need bespoke modules or workflow extensions. A subset need dedicated tenancy rather than shared multi-tenant. We cover all three under one engagement model.

  • ERP integration into accounting and finance systems
  • CAD integration including PLS-CADD for transmission engineering
  • Identity provider and single sign-on integration
  • Custom modules, workflow extensions and reports
  • Dedicated single-tenant hosting for enterprise and regulated workloads
PILLAR 03
4
Services in this family

Advisory & Operations

Services that continue past go-live. Some are advisory, like the knowledge-loss diagnostic that runs before implementation and the cost benchmarking that becomes available once you have history in the platform. Others are operational, like ongoing training and support.

  • Knowledge-loss diagnostic, a structured pre-implementation assessment
  • Cost benchmarking against anonymised platform averages
  • Refresher training and power-user certification
  • Standard and premium support tiers
  • Annual platform health-check and configuration review
Scattered project records before implementation
Why services exist

Most customers arrive with the same problem.

The estimating logic is in three different places: a senior engineer's head, a master spreadsheet, and a folder of past quotations no one has ever organised properly. The supplier records are in the accounting system, the project schedules are in someone's local file, and the variations are in email threads.

Every new project starts by reassembling all of this from scratch. Each tender quietly costs the company more than it should because nobody can find what was learned on the last similar one. Each handover is harder than it should be because the knowledge isn't in one place yet.

QBaticEPM3 collapses these into one record per project. But the platform doesn't make the move on its own. The services do. The licence is the start of the work, not the end of it. Almost every customer gets more value from a properly scoped implementation than from the licence alone, because the move from scattered to consolidated is where the savings actually come from.

Typical pre-platform state
5+
Disconnected data sources
3
Tools touched per estimate
1
Person who knows it all
0
Audit trails that hold up

What every implementation actually includes.

The implementation engagement is the most common starting point. Whether you take any of the other services depends on what the business needs after go-live. These four things are in scope every time.

1
Dedicated Implementation Lead

A single named person from QBatic owns the engagement end to end. You don't get handed between departments mid-project.

8+
Sector Packs Available

Pre-built configurations for housing, power utilities, government, renewables, roads, rail, water and oil & gas pipelines.

100%
Data Preserved On Migration

Whatever existed in the source systems is in the platform after the move. Nothing is dropped, summarised or quietly rounded.

3
Engagement Formats

Fixed-fee, time and materials, or annual retainer. The right format for the work, not the same format forced on every customer.

Heavy infrastructure under construction

Heavy industry doesn't reward platforms that arrive and then leave you to figure it out alone.

How services are bought

Three engagement formats, depending on how the work is shaped.

The right format depends on the scope. Defined work goes on a fixed fee. Open-ended work runs on time and materials. Long-term partnership work sits on an annual retainer. We'll recommend the format that matches the engagement, not the one that suits us.

FORMAT 01

Fixed-fee

For defined scopes. A typical implementation, a single integration, a sector pack rollout. Scope is written, price is agreed, timeline is committed. If the scope changes mid-engagement, we re-quote rather than burn through hours invisibly.

Best for: implementations · integrations · sector pack rollouts
FORMAT 02

Time and materials

For open-scope work. Custom develoEPMnt with evolving requirements, exploratory configuration during early adoption, multi-stage extension work. Daily rate, weekly timesheets, monthly billing. You see hours as they're spent, not at the end.

Best for: custom develoEPMnt · complex extension work
FORMAT 03

Annual retainer

For ongoing partnership. Continuous extension, advisory access, scheduled training cycles, prioritised support. Annual fee with an agreed allocation of service hours. Suits enterprise customers running multiple deployments or maintaining a long-term roadmap.

Best for: enterprise tenants · multi-deployment customers
Scoping conversation between QBatic and customer team

How we deliver, and what we won't do.

  • 01

    Documented before billed

    Every service engagement has a written scope, a written price and a written timeline before any work is invoiced. If the scope shifts mid-engagement, we stop and re-quote rather than continue burning hours against a brief that no longer fits.

  • 02

    Configuration over code

    The first answer to a customer requirement is always platform configuration. Custom develoEPMnt is offered only when configuration genuinely will not reach the requirement. This keeps the work upgrade-safe and avoids creating bespoke code that turns into a maintenance liability later.

  • 03

    Sector experience reused

    Where similar work has been done before in the same sector, the prior experience is brought into the new engagement. You don't pay to have us re-learn what's already been solved on another customer's project. The sector packs exist because of this.

  • 04

    Knowledge transfer at every step

    Your team owns the configuration, not the consultancy. Every implementation includes hand-over documentation, internal-champion training and the working configuration written up in a form your administrators can maintain after we leave.

  • 05

    No service-hours lock-in

    If you decide to bring service work in-house, or move it to another partner, the path out is clean. The configuration is yours, the data is yours, the documentation is yours. We'd rather earn renewals than make leaving painful.

Talk to us

Set up a scoping conversation against your own situation.

Request a Briefing Read the Company Profile