Services · Ecommerce development · AI platform subscription sites
Codeeo delivers AI platform subscription website development London founders and product teams rely on to turn a working model into recurring revenue. We build the pricing pages, sign up and checkout, usage metering, multi-currency recurring billing, tax handling for buyers in the UK, Europe and the US, and the account area where customers manage seats, credits and invoices. London AI companies rarely sell only to London, so the commercial layer has to cope with three currencies and several tax regimes from the first invoice.
Your models, prompts and product interface stay in your hands. Our work is the part customers touch when they choose a plan, pay, upgrade, query a charge or leave, and the records your finance team and investors read afterwards.
200+ companies servedFrom a first store to an ADX listed developer
What we build
Most AI companies in London reach paid plans in a hurry. A pilot customer wants an invoice, an investor asks for revenue figures, and the first international sign ups arrive before anyone has decided how to charge VAT to a German business or sales tax to a Texan one. Pricing is rarely simple either: a platform fee, included tokens or credits, overage, a separate rate for premium models, and annual commitments for larger accounts. What follows is the set of parts we usually deliver, adjusted to your pricing and your buyers. Each one is designed so that a number on an invoice can be traced back to the usage events and plan rules that produced it, because sophisticated buyers in the City and in US procurement teams will ask exactly that.
Plan tables shown in sterling, euros or dollars depending on the visitor's location or choice, with prices set per currency rather than converted on the fly. VAT inclusive display for UK consumers, exclusive display for businesses, and clear wording on what each tier includes, so the price shown is the price charged with nothing added at checkout.
International buyers see a sensible price in their own currency before they talk to sales.
Your platform posts usage events for tokens, inference minutes, documents processed or agent runs. We aggregate them per workspace and period, discard duplicate retries, and keep a ledger for prepaid credits that shows grants, consumption and expiry. Any disputed line can be rebuilt from raw events.
Usage invoices that survive a customer's finance team checking them.
UK VAT on domestic sales, reverse charge wording for overseas business customers, registration logic for EU consumers through the non-Union OSS scheme, and US sales tax calculation in states that tax software services, usually through a tax engine your adviser approves. Each invoice records which rule applied and why.
Tax decisions made by rules your accountant signed off, not by guesswork at month end.
Single sign-on through SAML or OpenID Connect, SCIM provisioning so a customer's IT team adds and removes users from their own directory, and seat counts that follow those changes into billing. Domain capture stops staff at a large client creating stray personal workspaces on card.
Large accounts pass procurement without a custom build for each one.
Annual or multi-year commitments drawn down by usage, with rates agreed per contract, purchase order numbers on invoices and bank transfer terms. Sales issues a quote from the same system, and once signed it becomes a live subscription with the agreed rate card attached.
Contract and self-serve revenue reported together, without spreadsheets in between.
Cards with Strong Customer Authentication on the first payment and merchant initiated renewals after that, Apple Pay and Google Pay for individual plans, and Bacs Direct Debit for UK businesses that prefer not to put software on a company card. Overseas customers can pay by card or local transfer where your provider supports it.
Fewer renewals failing because the bank wanted a second authentication.
Retry timing tuned per payment method, reminder emails, a secure link to update card details without logging in, and rules you choose for what happens to API keys while payment is outstanding: full service, a reduced rate limit, or suspension after a grace period.
Failed renewals recovered without cutting off a customer's production traffic by surprise.
A self-serve area for plan changes with proration shown before confirmation, seat management, spend caps, usage graphs by project or API key, invoice downloads and tax details. Billing owners and engineers get different permissions, so a developer can see usage without changing the plan.
Support stops answering the same invoice and seat questions every week.
Recurring revenue, usage revenue, net retention, churn and deferred revenue on annual prepayments, drawn from billing records and pushed to your accounting package and data warehouse. The figures in a board pack match what the ledger says.
Due diligence questions answered from a system, not reconstructed under deadline.
Who this suits
London's AI companies range from research spinouts near King's Cross to product teams in Shoreditch and fintech builders around Canary Wharf and the City. Their billing problems differ more than their technology does. Some need AI platform SaaS website development London buyers and US prospects will trust at first glance; others already have revenue and need AI platform subscription platform development London auditors can follow. All of our work runs remotely by video call, which suits teams already used to selling and supporting customers they never meet in person.
Your free tier has users in thirty countries and you are about to charge them. We help you pick a payment and tax setup that will not need replacing in a year, decide early whether a merchant of record suits you better than selling in your own name, and launch a short list of plans with metering on the one metric that drives your compute bill.
Start narrow, but with tax and currency handled properly.
Self-serve revenue is healthy and enterprise prospects are asking for single sign-on, purchase orders, security documentation and annual contracts. We add the contract layer, identity integration and quote to subscription flow alongside your existing card customers, so the sales team stops building invoices by hand and finance sees one revenue picture.
Contracts and card billing in the same records.
Banks, insurers and asset managers in the City treat an AI vendor as a third party they must oversee, and their procurement teams ask detailed questions about data location, retention and audit trails. Your billing and account area should answer those questions: usage logs customers can export, invoice records kept for the agreed period, and clear separation between customer workspaces.
Billing records that support your customer's own compliance work.
A London creative or consultancy business has built an internal AI tool clients now want to use directly. We turn it into a product with plans, sign up, payment and a client console, while keeping existing retainer clients on invoiced terms until they choose to move across.
A new revenue line without disrupting current clients.
Working together
Codeeo has no London office. Our team of 80+ people works from Dubai, Riyadh and Karachi and runs London projects remotely, with discovery, design reviews and acceptance testing all done by video call and shared documents. We have delivered 200+ projects across the UAE and the US and are rated 4.7 from 23 Google reviews. For AI billing work that remote model rarely matters: the decisions sit with your founders, finance lead and engineers, and we keep a written record of each one so nothing depends on who was in the room.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
We usually build the pricing site in Next.js, with billing on a provider such as Stripe Billing, Chargebee or Paddle, and usage pipelines in Node.js or Python feeding your warehouse. Final choices follow your pricing model, your tax position and your existing stack.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
Everything between a visitor reading your pricing and finance closing the month.
That means the public pricing pages, sign up and checkout, the billing engine configuration, usage metering from your platform, tax handling, invoices and credit notes, dunning, the customer billing console and reporting into your accounting system. We do not build or tune your models, and we do not describe mobile app features here; the work is the commercial website and platform around your product. If you already have parts of this in place, such as a working Stripe account, we extend what exists rather than starting again.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
React
Next.js
TypeScript
Node.js
Laravel
WordPress
Shopify Plus
WooCommerce
BigCommerce
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio