A 30-agent support team on a mid-tier SaaS ticketing platform is looking at roughly £20,000 a year in licence fees alone. Add AI features, phone integration, extra mailboxes, and a couple of custom integrations, and it is closer to £30,000. Every year. With no ceiling.
That is before you deal with the real frustration: rigid workflows that do not match your process, per-agent pricing that punishes growth, and integrations that break every time the vendor deprecates an API.
We build ticketing systems from scratch for UK businesses. You own the code, you stop paying per seat, and the software works the way your team actually works.
Why off-the-shelf ticketing tools fall short
The conversations we have with businesses tend to follow the same pattern. The SaaS tool worked fine when the team was small, but things have shifted.
Per-agent pricing does not scale. A 20-agent team paying £55 per agent per month is spending £13,200 a year on seats alone. At 50 agents, that is £33,000. And that is before premium features, AI add-ons (some platforms charge per resolution), and phone channel licences that run £50-£200 a month extra.
Workflows are too rigid. Multi-level approval chains, conditional routing based on product category or customer tier, and complex escalation rules either require expensive enterprise plans or simply are not possible. You end up forcing your process into the tool’s structure.
Integrations are shallow. SaaS platforms offer pre-built connectors for common tools, but connecting to a legacy ERP, a bespoke CRM, or an industry-specific system typically means custom API work costing £5,000-£30,000, and ongoing maintenance when either side changes.
Reporting misses the point. Dashboards show standard metrics, but if you need to track performance against your own SLA tiers, break down costs by customer segment, or correlate ticket data with external systems, you hit walls quickly.
Vendor lock-in is real. Exporting historical ticket data from most platforms involves CSV exports, manual field mapping, and weeks of migration effort. The switching cost keeps you paying, even when the tool no longer fits.
Teams end up building workarounds in spreadsheets and shared inboxes. The ticketing system that was supposed to bring order becomes another thing to manage around.
What we build instead
We start by mapping how your team actually handles requests today, including the workarounds, the manual steps, and the exceptions. Then we build the software to match.
Your workflows, encoded properly. Conditional routing based on ticket content, customer type, product, location, or any combination. Multi-level approvals. Escalation chains that reflect your real management structure. The business logic lives in the system, not in someone’s head.
No per-seat fees. You pay for the build, then it is yours. Add agents, departments, or locations without worrying about how it affects the bill. For teams over 50 agents, the cost difference over three to five years is substantial.
Integrations that actually work. Direct API connections to your CRM, accounting software, ecommerce platform, communication tools, or legacy systems. Bi-directional sync where you need it, not just a one-way data push. We build the connectors, so when something changes, we fix it — you do not wait for a third-party vendor to update a plugin.
UK GDPR compliance built in. Encryption in transit and at rest, role-based access controls, full audit trails with tamper-proof timestamps, automated data retention policies, and right-to-erasure workflows. UK hosting available if data residency matters to your sector.
Designed to grow. The architecture supports adding new channels (Slack, Teams, WhatsApp), new business units, or multi-brand configurations without a rebuild. Phase 1 gets you live; later phases add depth.
Features we typically build
Every project is different, but these are the modules that come up most:
Ticket intake and management
- Multi-channel capture: email (IMAP/SMTP with proper threading), web forms, live chat, Slack, Microsoft Teams, phone
- Ticket lifecycle management: open, in progress, waiting, resolved, closed — with custom statuses where needed
- Custom fields tied to your data model (account IDs, contract values, product categories, SLA tiers)
Routing and automation
- Automatic assignment based on skills, workload, department, priority, or content
- Conditional routing rules that non-technical staff can configure
- Scheduled automation (escalate unresolved tickets after X hours, notify managers on SLA breach)
- Macros and canned responses for common ticket types
- Batch actions for bulk assignment, status updates, and closures
SLA tracking and escalation
- Response time and resolution time targets per priority level, customer tier, or contract
- Automated breach warnings and escalation to named managers
- SLA compliance dashboards with real-time status
Self-service and knowledge base
- Customer portal for ticket submission, status tracking, and history
- Searchable knowledge base with auto-suggested articles during ticket creation
- Reduces ticket volume by letting customers find answers themselves
Reporting and analytics
- Real-time dashboards: queue depth, agent availability, SLA status, ticket volume
- Historical analytics: trend analysis, period-over-period comparison, heatmaps for peak times
- Agent performance scorecards: response time, resolution time, first-contact resolution, CSAT
- Custom report builder with scheduled email delivery and CSV/PDF export
Collaboration and communication
- Internal notes, @mentions, and ticket reassignment
- Bi-directional Slack and Teams integration (create tickets from messages, push updates to channels)
- Customer notifications at each status change
Security and compliance
- Role-based permissions so agents only see what they should
- Full audit logging: every edit, assignment, and access tracked with user and timestamp
- Data encryption at rest and in transit
- GDPR data export and deletion workflows
- SSO integration (SAML/OIDC) with Azure AD, Okta, or Google Workspace
Integrations
- CRM: HubSpot, Salesforce, Pipedrive — customer context (account, purchase history, lifetime value) in the ticket view
- Accounting: Xero, QuickBooks, Sage — link tickets to invoices, projects, or cost centres
- Ecommerce: Shopify, WooCommerce — order details, return status, and inventory visible in tickets
- Payments: Stripe, PayPal — verify payment status and process refunds from within a ticket
- Communication: Slack, Microsoft Teams, email, SMS
- Custom APIs for legacy or industry-specific systems
How we build it
Discovery and planning (2-4 weeks) We talk to the people who will actually use the system — agents, managers, and administrators. We document current workflows, identify bottlenecks, map required integrations, and define what an MVP looks like. Data migration planning starts here in parallel, not at the end.
MVP development (8-14 weeks) We build the core first: ticket intake (email and web forms), basic routing, agent collaboration, SLA tracking, simple reporting, and a customer self-service portal. You see working software every two weeks and can redirect priorities as needed.
Phase 2 development (6-10 weeks) Once the core is live, we add depth: omnichannel expansion (Slack, Teams, chat, social media), CRM and accounting integrations, advanced automation, knowledge base, and satisfaction surveys. Skill-based routing and custom dashboards typically land here too.
Testing and deployment (2-4 weeks) Thorough testing across all channels and integrations. We roll out in phases — often starting with one department or team — so the transition does not disrupt live operations.
Training and support (ongoing) Separate training sessions for agents, managers, and administrators, with written documentation and video walkthroughs. Twelve months of included support. After that, we offer maintenance plans or full handover to your IT team.
What it costs
Custom development costs more upfront than signing up for a SaaS subscription. But the long-term economics usually favour the build, especially for larger teams.
To put it in context: a 30-agent team on a mainstream platform typically spends £80,000-£150,000 over five years on licensing, add-ons, and integration maintenance. That figure climbs steadily with headcount, and you never own anything at the end.
A custom build has a higher initial investment, but:
- No per-agent fees. Adding staff does not increase your software cost.
- No annual price rises or forced plan upgrades.
- You own the code and the data as business assets.
- Optimised workflows and automation reduce handling time and agent overhead.
- Integrations are built to your specification, not limited to what the vendor offers.
We scope every project individually and give you a clear, fixed quote during a free consultation. No hidden fees, no surprises at renewal.
Industry use cases
Retail and ecommerce Customer service spanning product queries, order tracking, returns, and refunds. Tickets linked directly to Shopify or WooCommerce orders so agents see the full picture. Return workflows automated with approval steps and stock updates.
Financial services Client enquiries with FCA-compliant audit trails and data retention (five years for regulated records). Complaint management workflows with mandatory escalation paths. GDPR and data residency built into the architecture.
Healthcare Patient communications, appointment changes, prescription queries, and billing questions. Encryption, access controls, and audit logging for patient confidentiality. Integration with clinical or practice management systems.
Property management Tenant maintenance requests with job scheduling, contractor assignment, and status tracking. Landlord and tenant portals with different views of the same data. SLA tracking per property or management agreement.
Hospitality Guest requests, room changes, and special accommodations tracked centrally. Integration with property management systems (PMS). Staff actions logged for accountability and service recovery.
IT service desks Internal employee support: password resets, equipment requests, access provisioning. Self-service portal with approval workflows. Integration with Active Directory and asset management. ITIL-aligned if needed.
Education Student support and IT helpdesk. Separate portals for students and staff. Integration with student information systems. SLA tracking for response commitments.
Multi-brand and multi-site businesses Isolated data, branding, and workflows for each brand or location. Central reporting across all sites. One system, multiple tenants — without paying for separate SaaS instances per brand.
Common Questions About Custom Ticketing Systems
How does custom development cost compare to SaaS ticketing tools?
Upfront costs are higher, but the long-term maths usually favours custom. A 30-agent team on a mid-tier SaaS platform typically spends £60,000-£80,000 over three years once you factor in per-agent fees, AI add-ons, extra mailboxes, and integration costs. A custom build amortises over the same period with no per-seat fees and no annual price rises. You also end up owning the software as a business asset.
What's the typical development timeline?
An MVP covering ticket intake (email and web forms), basic routing, SLA tracking, agent collaboration, and simple reporting typically takes 3-5 months. Phase 2 adds integrations (CRM, Slack, Teams), advanced automation, and a knowledge base in another 2-3 months. We prioritise getting core functionality live first so your team can start using it while we build out the rest.
How do you handle updates and changes after launch?
All projects include 12 months of support covering bug fixes, minor adjustments, and security patches. After that, we offer flexible maintenance plans or can hand off to your internal IT team with full documentation. Because you own the code, you are never locked in.
Can you integrate with our existing systems?
Yes. Common integrations include CRMs (HubSpot, Salesforce, Pipedrive), accounting tools (Xero, QuickBooks, Sage), ecommerce platforms (Shopify, WooCommerce), communication tools (Slack, Microsoft Teams), and SSO providers (Azure AD, Okta, Google Workspace). We also build custom API connectors for legacy or industry-specific systems that SaaS platforms do not support natively.
What about data security and GDPR compliance?
We build to UK GDPR standards from day one: encryption in transit and at rest, role-based access controls, full audit logging with tamper-proof timestamps, data retention policies with automatic purging, and right-to-erasure workflows. We can host on UK data centres if data residency matters to your sector. For regulated industries (financial services, healthcare), we incorporate sector-specific requirements like FCA-compliant complaint handling or NHS data confidentiality rules.
Do you provide training for our team?
Yes. We run separate sessions for agents (4-8 hours covering ticket workflows, automation, and the customer portal), managers (2-4 hours on dashboards, SLA monitoring, and escalation), and administrators (4-8 hours on configuration, user management, and integrations). We also provide written documentation and video walkthroughs for ongoing reference.
When does it make more sense to stick with off-the-shelf software?
If your team is under 20 agents, your workflows are fairly standard, and you do not need deep integrations with legacy systems, a SaaS tool like Help Scout or Freshdesk will probably serve you well. Custom development makes most sense when per-agent pricing is becoming expensive, your approval workflows or routing logic are too complex for SaaS configuration, you need tight integration with internal systems, or you have compliance requirements that off-the-shelf tools do not fully cover.