Teams arrive asking for a bespoke build because the default checkout is off-brand, the invoice is wrong, or the pricing model will not fit. Almost all of it is catalog design, templates and entitlements. We configure first, extend only where the platform genuinely stops, and tell you which one you are buying before the work starts.
Trusted by 500+ organizations — including SaaS, subscription and usage-based businesses running their quote-to-revenue operations on Salesforce, HubSpot and Chargebee with Twopir Consulting.
Customization Scope
These are the reasons businesses tell us they need bespoke billing development. In most cases the platform already does it — the previous implementation just never configured it.
A default-styled checkout at the moment of payment costs conversion. Chargebee's hosted pages are brandable, and where that is not enough its in-app components let you build the flow inside your own application without holding card data.
Invoice layout, fields, line-item grouping, logo, legal entity details and language are template work. So is the quote document. Rebuilding invoice generation in-house is one of the most expensive mistakes we are asked to unwind.
Almost always it does — as a hybrid of the supported models. Flat fee, per unit, tiered, volume, stairstep and package pricing combine with included-usage quotas and overage rates to express most commercial models without code.
That is entitlements. Features map to plans, addons and charges with entitlement levels, and item-price entitlements let a specific price point carry different limits — so the product reads what was bought rather than inferring it from a plan name.
Dunning notices, renewal reminders, payment receipts and failed-payment emails are all templated and can be sent from your domain — or suppressed entirely so your own lifecycle tooling owns the conversation.
Custom fields and metadata carry your own attributes on customers, subscriptions and invoices, and they sync through to the CRM. A parallel database keyed on customer id is rarely the right answer.
This is the table almost no competitor page will show you, because it shrinks the scope of what they can bill for. It is also the single most useful thing we can tell you before an engagement starts.
| Requirement | How it is delivered | Who maintains it afterwards |
|---|---|---|
| Plans, addons, charges and price points | Configuration — product catalog. | Your team, from the admin UI. |
| Tiered, volume, stairstep or package pricing | Configuration — pricing model on the item price. | Your team. |
| Hybrid plan plus metered usage with included quota | Configuration — metered features and entitlement-based usage billing. | Your team, once the meters are defined. |
| Feature access by plan or price point | Configuration — product and item-price entitlements. | Your team. |
| Branded checkout and self-serve portal | Configuration and theming on hosted pages. | Your team; we hand over the theme. |
| Checkout embedded inside your own application UI | Extension — in-app components against the API, with tokenisation so card data never touches your servers. | You own the front-end code; Chargebee owns the card handling. |
| Invoice, credit note and quote documents | Configuration — document templates per entity and language. | Your team. |
| Notification and dunning emails | Configuration — email templates, or suppressed so your own tooling sends them. | Your team, or your lifecycle platform. |
| Custom attributes on customers or subscriptions | Configuration — custom fields and metadata, which sync to the CRM. | Your team. |
| Approval routing on negotiated quotes | Configuration — CPQ approval rules. | Your team, once the rule set is designed. |
| Aggregating raw product events before they are billable | Extension — a usage pipeline you own, emitting clean events into Chargebee. | You own it. This is real engineering, permanently. |
| Provisioning your application on a subscription change | Extension — a webhook consumer, idempotent on event id. | You own it, with a replay path and a dead-letter queue. |
| A CRM object model the managed package does not cover | Extension — custom objects, flows or Apex on the CRM side. | You own it; we build and document it. |
Configuration work is covered in Chargebee subscription and billing automation — lifecycle, usage and entitlement configuration Chargebee API and integration development — and everything past the boundary is custom development Chargebee consulting services — the Chargebee practice these sit inside
Customization is not decoration. Each of these areas moves conversion, support load, or how quickly you can launch a new commercial model.
The highest-leverage surface in the whole system. A branded, short, correctly localised checkout converts better than a default one, and the difference compounds across every acquisition channel.
Every upgrade, plan change, payment-method update and invoice download a customer can do themselves is a support ticket that never opens.
Modelling your pricing so the awkward deals are expressible in the catalog rather than handled as exceptions by a person every renewal.
The link between what a customer bought and what your product lets them do — read from the billing record rather than inferred from a plan name in your code.
Invoices, credit notes, quotes and every lifecycle email, templated per entity, language and market so nothing customer-facing looks generic.
Custom fields, metadata and the CRM-side object model, so your own attributes travel with the record instead of living in a spreadsheet keyed on customer id.
Four stages. The second one regularly ends the engagement early because the answer turns out to be a setting, and we would rather tell you that than bill for a build.
We take the requests as stated — the checkout, the invoice, the pricing model — and translate each into what it actually needs the system to do.
We attempt every requirement as configuration in a test site first. Whatever works is done, documented and handed to your team. What remains is the real custom scope.
For what is genuinely left, we design it explicitly: what it does, where it runs, how it fails, who maintains it, and what it costs to own in a year.
Extensions ship with tests, a runbook and idempotent event handling. Configuration ships with a walkthrough so your team can change it without us.
Some customization only works if the surrounding systems move with it. These are the connection points that customization work usually touches.
Custom fields and metadata defined on Chargebee customers and subscriptions map through the managed package onto the Salesforce Account and subscription object, so the attributes your team added are reportable in the CRM rather than trapped in billing.
Plan, entitlement level and subscription state land on the HubSpot record so lifecycle marketing and CS can segment on what a customer can actually do, not just what they pay.
The application reads entitlement data from the billing record rather than hard-coding plan names, so a new packaging tier is a catalog change instead of a release.
Quote documents built from the live catalog carry your terms and branding, and acceptance triggers the subscription — so the signed paper and the billing record cannot diverge.
Where invoices are templated per legal entity, tax determination through Avalara has to match the entity and nexus on each template, or the branding work quietly creates a compliance problem.
Lifecycle and dunning emails sent from your own domain with proper authentication, or suppressed in Chargebee entirely so your marketing automation platform owns the whole customer conversation.
Tailoring a commercial system to how a business actually operates is the core of Twopir's work across platforms.
Quoting, approval routing and document generation shaped around a real sales process rather than the platform's defaults.
Billing behaviour and financial documents tailored to the client's entity structure and reporting requirements on the CRM record.
Field-level customization across two platforms so each team saw the attributes it needed without either system becoming the other's dumping ground.
We help growing and mid-market companies solve complex CRM, integration and business system challenges, and we work with enterprise organizations on the same problems at larger scale. Knowing what not to build is part of that.
Every requirement gets tried as configuration in a test site first. It regularly ends engagements early. We would rather lose the build revenue than hand you code you have to maintain for the next five years.
Every extension we propose comes with an honest view of what it costs to own — upgrades, edge cases, the person who has to understand it when the author leaves. That number changes decisions.
Most "our pricing does not fit" conversations end with a hybrid of supported pricing models and an entitlement structure. Modelling it properly is cheaper than building around it, and it means your team can launch the next plan without us.
As a Salesforce Partner and HubSpot Partner we extend the CRM object model alongside the billing one, so a custom attribute is reportable everywhere it matters rather than stranded in one system.
Themes, templates, entitlement maps and catalog structure come with a walkthrough for your team. Customization that only the consultancy understands is just a subscription to the consultancy.
More than most teams expect. The product catalog, pricing models, entitlements, metered features, dunning and retry sequences, approval rules, checkout and portal theming, invoice, credit note and quote templates, notification emails, and custom fields on customers, subscriptions and invoices are all configuration. Code becomes necessary when you need your own logic in the path — a usage pipeline, a provisioning service, or a checkout embedded inside your own application UI.
Yes, at two levels. Chargebee's hosted pages can be themed to your brand system, which covers most cases and keeps you out of card-data scope entirely. Where the flow has to stay inside your own application, in-app components let you build the UI while tokenisation keeps card details off your servers. The second option is real front-end work you will own, so we only recommend it when the hosted page genuinely cannot carry the experience.
Usually, as a combination rather than a single model. Chargebee supports flat fee, per unit, tiered, volume, stairstep and package pricing, and those combine with included-usage quotas and overage rates to express hybrid models — a platform fee granting an entitlement quota with usage beyond it billed per unit, for example. Bring us the three deals you think will not fit; that conversation is usually short.
Entitlements are the mapping between what a customer bought and what your product lets them do. Features and their levels attach to plans, addons and charges, and item-price entitlements let individual price points carry different limits. You need them as soon as your application is checking plan names in code — that pattern breaks the first time you launch a variant or grandfather a legacy customer.
Yes. Invoice, credit note and quote documents are templated, and templates can vary by business entity and language, which is what multi-entity and multi-market businesses need. Be aware that customised invoices and tax determination have to stay aligned — a template pointing at the wrong entity is a compliance problem, not a design one.
Configuration will not. Themes, templates, catalog structure and entitlements move forward with the platform. Extensions can, which is exactly why we push them to the last resort: anything you build against the API is code you test against future releases. We keep the custom surface as small as the requirement genuinely allows.
We hand it over. Configuration comes with a walkthrough so your team can change themes, templates, catalog entries and entitlement maps without us. Extensions ship with tests, a runbook and idempotent event handling. Retained support is something clients choose because the commercial model keeps evolving, not because they cannot operate what we built.
Bring us the requirements that look like custom development. We will attempt each one as configuration in a test site, tell you plainly what is left, and price the remainder with the maintenance cost included.
Configuration first — and an honest answer about what really needs building
