Skip to content
BrightonSolution

Services

What we build and run for you

Seven services that cover the life of a software product, from the first specification to the years of running it. Each one sets out what we do, what you receive and who it suits.

Custom Software Development

Good for
Companies whose workflows, data or compliance needs have outgrown ready-made products.

When spreadsheets, plugins and generic SaaS stop keeping up, we build software around how your company actually works. That means internal platforms, customer portals, integrations between the tools you already use and the back-office systems nobody else wants to touch. Every system is designed to be understood and extended by whoever maintains it next.

What you get

  • Requirements and technical specification
  • System architecture and data model
  • Back-end services and APIs
  • Admin and internal user interfaces
  • Integrations with existing tools and third-party APIs
  • Documentation and handover
First step
A working session to map the process the software has to support, then a written specification and estimate for a first release.
From our work
EventErp, Recruitment Suite, Leadpin. See the work

Web Application Development

Good for
Startups launching a product and established businesses replacing a site or portal that has become a liability.

We build web products end to end: the public-facing site, the logged-in application behind it and the APIs that connect them. We favour proven frameworks, server-side rendering where it matters and measurable performance budgets. The result is a product that loads quickly, works on every device and is easy for your team to update.

What you get

  • Front-end built with React or Next.js
  • REST or GraphQL API layer
  • Authentication, roles and permissions
  • Content management where you need to edit copy yourself
  • Performance, accessibility and SEO baseline
  • Automated tests and deployment pipeline
First step
A review of the current site or product, if there is one, and a short specification covering pages, user roles, integrations and performance targets.
From our work
FlexyPdf, WeekendCart, Empire Event. See the work

Mobile App Development

Good for
Products where the phone is the main interface: field teams, consumer services, bookings, loyalty and on-demand businesses.

We build mobile apps that are designed for the platform they run on and the people who use them. Depending on your product and budget, that can mean a single cross-platform codebase with React Native or Flutter, or fully native Swift and Kotlin. We handle the whole lifecycle from store listings and release builds to crash reporting and updates.

What you get

  • Cross-platform or native app for iOS and Android
  • Offline support, push notifications and deep links
  • Secure API and account management
  • App Store and Google Play submission
  • Analytics and crash reporting setup
  • Release process for ongoing updates
First step
A decision on native versus cross-platform based on your features, team and budget, written up with the trade-offs.
From our work
Ten Android apps published on Google Play as Brighton Solution. See the work

Cloud & DevOps

Good for
Teams that deploy by hand, cannot see why things break, or are paying for far more cloud than they use.

We set up and operate cloud environments on AWS, Google Cloud and Azure using infrastructure as code, so every environment can be rebuilt from a repository rather than from memory. We put in place CI/CD pipelines, monitoring, backups and cost controls, and we document how it all fits together. If you already have infrastructure, we review it and fix what is fragile before it fails.

What you get

  • Cloud architecture review or design
  • Infrastructure as code with Terraform or Pulumi
  • Containerisation and orchestration with Docker and Kubernetes
  • CI/CD pipelines with automated testing and rollbacks
  • Monitoring, logging, alerting and backups
  • Cost and security review with written recommendations
First step
A read-only review of your accounts and deployment process, ending in a written list of risks and changes in priority order.

AI Integration

Good for
Companies with repetitive knowledge work, large document sets or support queues that need faster first answers.

We add language models, retrieval and automation to real products: search across your documents, assistants that answer from your own data, classification and extraction for documents and tickets, and workflows that draft rather than decide. We start by proving the use case on your data, measure the quality honestly and only then build it into production with logging, evaluation and human review where it belongs.

What you get

  • Use-case assessment and feasibility test on your data
  • Retrieval-augmented search and assistants over internal content
  • Document, email and ticket classification and extraction
  • Integration with OpenAI, Anthropic, Google or open-source models
  • Evaluation harness, logging and cost controls
  • Privacy and data-handling review
First step
A feasibility test on a sample of your own data, so you see what the model gets right and wrong before anything is built.

UI/UX Design

Good for
New products that need to be right the first time, and existing products whose interface is slowing people down.

Good design is what makes software usable without training. We map the flows your users go through, prototype the screens, test them with real people where possible and hand over a design system that engineers can build from directly. We design for accessibility from the first wireframe, not as a final check.

What you get

  • User flows and information architecture
  • Wireframes and clickable prototypes
  • High-fidelity screens for web and mobile
  • Design system with components and tokens
  • Accessibility review against WCAG 2.2 AA
  • Developer handover with specifications
First step
Conversations with the people who use the product today and a map of the tasks they need to complete, before any screens are drawn.

Maintenance & Support

Good for
Any business running software it depends on without an in-house team to maintain it.

Software needs looking after once it is live. We keep dependencies current, apply security patches, watch the monitoring, fix what breaks and make the steady stream of small improvements that keep a product useful. We can take over systems we did not build, starting with an audit so you know exactly what you have.

What you get

  • Codebase and infrastructure audit on takeover
  • Dependency, framework and security updates
  • Bug fixes with agreed priorities and timelines
  • Uptime monitoring and incident handling
  • Scheduled improvements and small features
  • Monthly report of work done and recommendations
First step
An audit of the codebase, infrastructure and access, so both sides know exactly what is being taken over and in what state.

Engagement models

Ways to work with us

Any service above can run under one of four commercial arrangements. The right one depends on how well defined the work is and how long it will continue.

Fixed Project

A defined scope, delivered for an agreed price and timeline.

Best for
Clearly specified products, MVPs, redesigns and migrations.
Billing
Fixed price, invoiced per milestone.

Dedicated Team

Capacity reserved for your product, led by us.

Best for
Products under continuous development that need stable, full-time capacity.
Billing
Monthly, based on the capacity reserved.

Time & Materials

Flexible capacity billed for the hours actually worked.

Best for
Evolving requirements, research-heavy work and ongoing improvements.
Billing
Hourly or daily rate, invoiced monthly.

Long-Term Partnership

An ongoing technology partner for companies without an in-house team.

Best for
Businesses that depend on software and want one team to own it over years.
Billing
Monthly retainer, reviewed quarterly.

Not sure which applies? Describe the work and we will recommend a model and explain the trade-offs.

Standard practice

What every engagement includes

Whatever the service or the commercial model, these are part of the work rather than extras.

  1. A written scope and estimate before work starts

    What will be built, what is out of scope, how long it should take and what it will cost, agreed in writing. Nothing starts on a verbal agreement.

  2. Reviewed, traceable changes

    Every change goes through a pull request with a written description and review before it reaches the main branch, so decisions remain traceable in your repository.

  3. A staging environment from the first sprint

    Working software is deployed somewhere you can open at any time, so progress is something you can click rather than a status report.

  4. Automated tests and a deployment pipeline

    Tests run on every change and deployments are scripted, so releases are repeatable and a bad one can be rolled back.

  5. Documentation and handover

    Architecture notes, a runbook and setup instructions, written so that an engineer who has never spoken to us can take over.

  6. A support window after launch

    After go-live we stay on to fix issues and answer questions for an agreed period, before any longer-term support arrangement begins.

Start a project

Tell us what you need to build.

Send a short note about your project and we will reply with honest next steps, whether or not that involves us.