One core platform. Everything else is opt-in.
There are no tiers to jump between. You license the 5 capabilities every retailer needs, then switch on any of the 4 modules the month they start earning their place.
One core, always on
Customers, market transactions, billing, the ledger, products and tax. There is no version of a retailer that does not need these, so they are not sold separately.
Modules you switch on
MarkeTrak, collections, settlements and the collaboration tools are entitlements. Enable one the month you need it; it appears in the product and on the invoice together.
Scoped to the book, not the seats
Retail energy headcount is a bad proxy for volume. Pricing follows accounts under management, so hiring a second billing clerk does not cost you more.
Compose your platform
Toggle the modules you'd actually turn on.
This is the same model as the product: entitlements on your organisation, independent of one another. Whatever you pick here travels with your enquiry, so the first conversation starts from your shape rather than ours.
Core platform
Included for every retailer
- Customers & enrollmentEvery prospect, customer, service address and ESI ID in one book of business — from first quote to an active account.
- Market transactionsThe full ERCOT document inventory, sent and received, with every chain tracked end to end.
- Billing & the ledgerA real double-entry general ledger under the bills — every invoice, payment, deposit and adjustment posts to it.
- Products & pricingDesign a plan, price it per utility, publish its EFL, and renew the customers on it.
- Tax & tariffsThe Texas bill stack, calculated rather than estimated — and the same engine behind your quotes.
Modules
Switch on what you run
0 of 4 selected
Your platform
- Core platform · 5 capabilities
No modules selected. The core alone enrolls customers, talks to the market and issues a correct bill.
Pricing is scoped to your accounts under management. Tell us the size of the book and we will give you a number, not a range.
Get a quoteNot an upsell
Included whatever you switch on.
Some things should never be a line item. These are ours.
- Implementation support and migration planning
- The simulated market, for testing before you go live
- Row-level change history and the operator audit trail
- Tenant isolation enforced at the application and the database
- Roles and granular permissions you define
- Every capability you enable, for every user you have
Questions
The ones retailers actually ask.
How does the modular pricing actually work?
You license the core platform, then enable modules individually. Each module is an entitlement on your organisation: switching it on makes it appear in the product and on your invoice at the same time, and switching it off removes both. There are no tiers to jump between and no bundle you have to buy to reach one capability.
Can we start with the core and add modules later?
That is the expected path. Most retailers start with the core, add collections once the book is big enough to have a real past-due problem, and add settlements when checking TDSP invoices by hand stops being possible.
What happens if we turn a module off?
Its screens and API surface disappear and you stop being billed for it. Your data stays — the records a module created are still yours and still exportable; you simply are not licensed to work them until it is re-enabled.
Which markets does Conduit support?
ERCOT, in Texas. The transaction catalog is Texas SET 5.0 and the issue-resolution workflows follow ERCOT's MarkeTrak taxonomy. Other deregulated markets are additions we scope with the retailer who needs them first.
Can we migrate a book we already have?
Yes. Customers, service accounts and open MarkeTrak cases import in bulk with column mapping, validation and a dry run that shows exactly what would be written before anything is.
Does this replace our EDI vendor?
Yes. Market transactions are part of the core platform, not an integration to one. That is the point: the enrollment, the meter read and the invoice all land against the same account, so nothing has to be matched up afterwards.
Who owns our data?
You do. Every object is readable through the API, and an export is a request away with no exit fee attached to it.
Can we try it before committing?
Yes. Conduit ships a simulated market: submit a switch, a move-in, a rejection or a permit hold and watch the whole chain play out against test accounts before a single real customer is enrolled.
How long does implementation take?
It depends on the size of the book you are moving and how clean it is. We scope it with you before you sign anything, and we would rather give you a real date than a fast one.
Tell us the size of your book.
Accounts under management, the markets you serve, and which modules you'd switch on. That is enough for a real number rather than a range.