Services · Ecommerce development · AI meeting assistant subscription sites
Codeeo delivers AI meeting assistant subscription website development Manchester software companies use to turn sign ups into recurring revenue. We build the pricing pages, checkout, pooled usage billing and account area for products that record, transcribe and summarise calls. Manchester buyers are a particular mix: digital agencies in the Northern Quarter, production teams at MediaCityUK in Salford, professional firms in Spinningfields and university research groups. Each pays in a different way, and the subscription platform has to handle all of them cleanly.
We do not build the recorder or the speech model. We build the commercial layer around it: what customers see, what they pay, how usage is counted and how a team changes its plan without writing to support.
200+ companies servedFrom a first store to an ADX listed developer
What the platform includes
Selling a meeting assistant to a Northern Quarter agency is not like selling it to a university. The agency wants to bill its own clients for recorded workshops; the university needs a purchase order, a supplier record and an invoice addressed to a department. A broadcaster's production office cares about who can see contributor interviews, and a Spinningfields firm wants to know where transcripts are stored before anyone signs. The capabilities below are chosen for those buyers. They share one billing system and one product API, so a change of plan, a new seat or a usage spike is reflected in the product and on the next invoice at the same time. Nothing here is fixed: most vendors launch with four or five of these parts and add the rest as the customer mix becomes clearer.
Hours are bought at workspace level and shared by everyone on the team, rather than locked to individual seats. A producer who records all day draws from the same pool as a colleague who records once a week, and the admin sees the remaining balance on one screen.
Teams buy what they use, not a seat each.
Agencies run separate workspaces per client, each with its own recordings, members and usage report. Usage can be exported per workspace so the agency recharges its clients accurately, and a client contact can be invited to view only their own meetings.
Agencies resell your product without spreadsheets.
Universities, councils and larger firms pay by invoice against a purchase order. The platform records the PO number, supplier references and payment terms, sends invoices to an accounts payable address and keeps the account active while payment is pending.
Institutional buyers can say yes without a card.
Many small Manchester firms prefer Direct Debit through Bacs for monthly software. We set it up alongside card payments, with mandates collected online, advance notice of each collection and automatic retry rules your provider supports.
Lower card failure and fewer expired card churns.
Owner, billing admin and member roles, with single sign on for customers on Microsoft Entra ID or Google Workspace. Billing staff see invoices but not recordings; producers see recordings but not card details. Roles are enforced in the product, not only hidden on screen.
Sensitive recordings stay with the right people.
Your product tells meeting participants they are being recorded; the website explains how, with a plain page for people who were recorded and want to know what happens to their data or ask for deletion. That page is linked from bot join messages and from every summary email.
Clear answers for people who never signed up.
A pricing page that shows seats, pooled hours, storage, integrations and retention side by side, with the recurring price including VAT where consumers can buy. Short worked examples show what a ten person team actually pays each month, which answers the question most visitors arrive with.
Fewer pricing emails, more direct sign ups.
Admins choose alerts at set points of the pooled allowance and a hard or soft cap. When the pool runs low, the platform offers a top up or an upgrade inside the account area instead of failing the next recording halfway through a client call.
Overage is a choice, never a shock.
Monthly recurring revenue, expansion from extra hours, churn and failed payments, broken down by plan and customer type. Founders reporting to investors or lenders get numbers that reconcile with the accounts, and can see which customer group, agency, media or academic, actually grows over time.
One version of revenue for the board and the bank.
Product tours and demo videos carry captions and a transcript, forms work with a keyboard and screen reader, and colour contrast meets WCAG 2.2 AA. University buyers in particular ask for an accessibility statement, and the Equality Act expects reasonable adjustments, so we publish one that describes the site honestly.
A site that passes accessibility checks in procurement.
Who this is for
Manchester's meeting assistant companies tend to grow out of a specific customer base, often agencies, media or the universities, before they widen. The first version of the subscription platform should fit the customers already paying you, not an imagined enterprise buyer. These are the four situations we see most, with the part of the build that usually comes first in each case. If your product serves more than one, we sequence the work so the largest source of revenue is ready first. Manchester and Salford are separate cities with separate councils, but for billing purposes they are one market, and we treat them that way.
Your early customers are Northern Quarter agencies recording discovery workshops and client calls. They need client workspaces, recharging reports and invoices that make sense to their finance person. We build those first, together with a plan structure that lets an agency grow from one client workspace to twenty without renegotiating anything. Partner pricing for agencies that bring several clients can sit in the same catalogue, applied automatically when the agency adds a workspace, so your team stops approving special rates by email.
Workspace billing before enterprise features.
Producers around MediaCityUK record interviews, edit meetings and contributor calls, often on short productions with temporary staff. Seats that can be added for a few weeks and released, retention set per production and strict access to contributor recordings matter more here than a polished enterprise order form. Production companies also tend to pay per production, so we let one account hold several billing entities and send each invoice to the right production accountant.
Short term seats need clear proration rules.
Research interviews and supervision meetings bring ethics approvals, data management plans and institutional procurement. Universities in Manchester buy through purchase orders and supplier onboarding, and often need data held in the UK. We build invoice billing, department level accounts and a documents area your champions can forward to their procurement and information governance teams.
You started with payment links and a manual list of who has paid. It worked for the first fifty customers and now nobody trusts the numbers. We move existing customers onto proper plans and payment methods, connect entitlements to your product and give finance a ledger they can reconcile. Because payment methods move through your provider, customers are not asked to type card details again, and anyone on a legacy rate stays on it until you choose to change it.
Existing customers keep their price unless you decide otherwise.
How we work together
We have no office in Manchester. The Codeeo team, 80+ people across Dubai, Riyadh and Karachi, works with Manchester and Salford clients remotely, and every workshop, review and demo runs by video call with written notes afterwards. Most clients take a fixed scope project for AI meeting assistant subscription platform development Manchester side, followed by a monthly retainer for pricing changes and integrations. Teams that already employ engineers can add dedicated developers to their own sprints instead. Whichever route you take, the code and billing accounts are yours from day one.
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
Typically Next.js or a headless CMS for the public site, Stripe Billing, Chargebee or Paddle for subscriptions, GoCardless for Direct Debit, and connections to Xero or QuickBooks. The final choice follows your team and your customers.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
Cost follows billing complexity and integrations, not the number of pages.
The main drivers are how many meters you bill on, whether you need pooled hours, PO invoicing or Direct Debit, how many systems the platform connects to, and whether existing customers must be migrated. A card only site with a few seat plans is a much smaller project than an agency and university ready platform. We price after discovery, with each driver listed so you can decide what goes in the first release.
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