Skip to content

Custom software development · Bristol

Custom software development in Bristol.

QalbIT builds custom software for Bristol companies from Ahmedabad, India: aerospace and advanced-engineering suppliers around Filton, the chip-design and deep-tech firms that gave the Bristol and Bath corridor its “Silicon Gorge” name, financial and professional-services firms in the city centre, and the animation, broadcast and games studios clustered around the harbourside. There is no QalbIT office in Bristol and no UK entity, and this page sets out exactly what that changes.

Bristol runs on engineering rigour in one half of the city and creative risk-taking in the other, and a lot of the interesting work sits where those two meet: a production tool for a studio, a certification tracker for an engineering supplier, a trading system for a fintech spun out of the city’s finance base. This page covers all three, including the rows where a firm nearer to hand is the better choice.

  • 2018

    Building custom software since

  • 120+

    Projects delivered

  • 4.5h+

    Live on UK time, every working day

  • 4.9

    Google rating, 18 reviews

Get your free estimate

Three quick questions: scope, approach and a price range back within 48 hours. No sales call required first.

What do you need built?
When do you want to start?
Where should we send the estimate?

Answer all three questions above, then send.

NDA-friendly · IP yours from day one

Definition


What custom software development in Bristol means when the developers are not in Bristol

Custom software development in Bristol means designing, building and running software shaped to one company’s own process: a certification tracker for an aerospace supplier at Filton, a production-scheduling tool for an animation studio, a client portal for a financial-services firm. QalbIT does that work as a remote engineering partner from Ahmedabad, India, live from 09:00 to 13:30 UK time in winter and to 14:30 in summer, under a contract governed by English law, with no office in Bristol.

The engineering does not change because the developers sit somewhere else. What changes is the clock, the contract and the way data protection is handled, and Bristol’s mix of regulated engineering suppliers and fast-moving creative and fintech companies tends to ask sharp questions about all three, from different directions.

A software house in Bristol or Bath is already inside your supply chain: someone can drive to Filton or the harbourside on a Wednesday, the invoice is domestic, and procurement approves the name without a second look. A partner outside the country has to earn that trust on paper: a scope that lists what is excluded, an architecture your lead engineer can take apart, a data protection position your compliance lead has read, and live hours across most of your day.

All of it is routine, and it costs far less to settle before a contract than after a customer’s supplier questionnaire finds the gap.

We are the remote option, so the case for and against us is written out below rather than discovered mid-project.

At a glance

  • What we build

    Certification and production-tracking systems, trading and client portals, SaaS products, mobile apps, integrations

  • Engagement shapes

    A first release · a rebuild of a system you have outgrown · modules over an ERP or a production tool · a standing engineering pod

  • Hours

    Remote from Ahmedabad, live 09:00 to 13:30 UK time in winter and to 14:30 in summer, Monday to Friday, written handover after that

  • Presence in the UK

    None. No office, no staff, no UK entity. Your MSA under English law, invoiced in pounds sterling

  • Who owns what

    Code, cloud accounts and IP in your company’s name, assigned as each piece is written

Definition


Bristol agency, contractor, or remote engineering partner

Three different things to buy, often compared on day rate as though they were one.

  • Bristol or Bath agency

    A locally registered firm on UK time all day, able to send people to your site at short notice. What you pay for is closeness and a domestic invoice. Choose it when the work needs people in a test cell or on a sound stage, when procurement expects a nearby supplier, or when the project runs on workshops.

  • Contractor or staffing firm

    Engineers billed by the day into a team you already run, while your own lead keeps architecture, code review and release. Choose it when an engineering manager on your side has time to direct more people.

  • Remote engineering partner

    A small senior team that takes responsibility for a defined build, works your morning and early afternoon from India, and hands you the repository. With no UK entity, the contract and the due-diligence paperwork have to be done properly first. Choose it when you know what the system must do and want it built right once.

QalbIT is the third. When one of the other two fits your company better, you hear that on the first call, before any money moves.

Fit


When a Bristol company should use a remote partner for custom software, and when it should not

Both sides of the argument, set out plainly. A page that only argues one side is not helping you decide anything.

  • Hire a remote partner when

    • Someone on your side can describe the process and make a decision about it without convening a working group.
    • The work has a defined shape, a first release, a rebuild, or a set of modules, rather than an open-ended programme with a shifting sponsor.
    • Four and a half to five and a half live hours a day are enough for what needs a conversation, and the rest can run on a written handover.
    • You want the source code, the pipeline and the documentation held in your own company’s accounts once the work is finished.
    • Personal or commercially sensitive data is in scope in the ordinary way, and whoever owns compliance on your side is willing to set the rules and check our evidence against them.
  • Hire locally instead when

    • A framework agreement, a client’s own terms or an export-control condition require a supplier established in the United Kingdom.
    • People have to be physically present: hardware in a test cell at Filton, a production shoot on a sound stage, a trading-floor rollout.
    • Your security policy forbids production access from outside the UK and the work cannot be done on masked data.
    • Delivery genuinely has to run on UK time until early evening because the people who decide are only reachable late in the day.
    • What you actually need is a contractor working under your own architect, in which case a staffing firm will cost less to manage.

What that looks like for a Bristol buyer

Suppliers into aerospace programmes at Filton run supplier audits that go well beyond price, and the fintech and deep-tech companies around the harbourside have absorbed a similar discipline from the venture investors and regulated customers they answer to. The questions that arrive are specific: where does the data sit, who can reach it, what is logged, how is an incident traced back to a cause. Those are exactly the questions we answer in writing before a project starts, with evidence of what we actually run rather than a general capability statement. The engineering base north of the city has its own research anchor. The National Composites Centre, owned and run by the University of Bristol, is the largest tenant of the Bristol and Bath Science Park at Emersons Green and one of the High Value Manufacturing Catapult centres. QalbIT has no connection with it; it is named because the composites and aerospace supply chain around it decides what a Bristol engineering firm must prove. Most of those firms work to the AS9100 series of aerospace quality standards, and some hold technical data that UK export controls restrict, which changes what an engineer in India may be allowed to see. Bristol projects that belong on the second list get turned down. A remote build that should have gone to a local firm ends up costing more than its fee, and the strain shows by the second sprint.

Next step


Not sure which list your project sits on?

Send us what the system has to do, what data it will hold and what your procurement rules say. You will get a straight answer, including “hire someone closer to home” when that is the honest one.

Comparison


Remote engineering partner vs a Bristol or Bath agency vs a contractor

Each row is a real difference, the losing ones included. There is no day-rate row: we hold no sourced figure for what West of England agencies charge, and an invented one would mislead you. Send us your scope, the kinds of data involved and your procurement rules, and we will fill this table in for your project rather than the general case.

Row-by-row comparison of a remote engineering partner, a Bristol or Bath agency and a contractor
Bristol or Bath agencyContractor or staffing firmQalbIT (remote partner)
Can be on your siteYesOftenNo
Live hours on UK timeAll dayAll day, in most cases09:00 to 13:30 (14:30 in summer), then a written handover
Architecture owned byThe agencyYour leadUs, reviewed with your technical lead
Testing and release owned byThe agencyYour leadUs, with your sign-off as the gate
Contract, law and currencyDomestic, English law, GBPDomestic, English law, GBPYour MSA, English law, invoiced in GBP
Source code and IPDepends on the contractYoursYours, assigned as each piece is written
Frameworks requiring a UK-established supplierEligibleUsually eligibleNot eligible
Team continuityShifts with agency workloadTurns over with the contractSmall, senior, named in the proposal, unchanged
  • 01

    The rows we lose are worth reading first.

    Being on site at Filton, all-day UK cover and eligibility for UK-only frameworks go to the local firms, and the table says so. Better to see that now than in month four of a contract.

  • 02

    Where data sits and where developers sit are two different questions.

    A platform can run in a UK region of your own AWS account, under keys you hold, while the people writing it sit in Ahmedabad under access rules you set. For ordinary personal data that settles most questions. For export-controlled technical data it does not, as the compliance section explains.

  • 03

    A staffing firm adds hands, not a system.

    Day-rate engineers add capacity to a team that already has direction. Without a lead on your side holding architecture, review and release, more of them means more code, not a working system sooner.

  • 04

    Export-control and framework eligibility are binary.

    If a defence-adjacent programme or a customer flow-down requires a UK-established supplier, engineering quality does not change the answer. Raise it on the first call and you will know the same day.

What we build


Custom software development services we deliver in Bristol

Systems that share one record, so a component, a client or a production asset moves through operations, finance and delivery without three people retyping it into three different tools.

  • Engineering

    Certification and production-tracking systems

    Certification tracking, non-conformance capture and supplier records for engineering firms supplying into aerospace programmes, usually replacing a shared drive and a spreadsheet nobody trusts fully.

  • Portals

    Client, investor and supplier portals

    A portal over the system a financial-services or professional-services firm already runs, with role-scoped access, document handling and an audit trail that survives review.

  • SaaS

    SaaS products and first releases

    Multi-tenant products with billing, roles and usage limits for a founding team out of the Bristol and Bath deep-tech corridor, shaped to reach paying users before the next funding round.

  • Mobile

    Mobile apps for people away from a desk

    One Flutter codebase for iOS and Android, for field technicians, delivery crews and production staff working sites where the signal is unreliable, built offline-first because that is where the work actually happens.

  • Integrations

    Engineering, finance and production integrations

    Wiring a quality-management system, a trading platform or a production-asset tracker to the tools around it, with queues, retries and a reconciliation view so a dropped message is seen rather than discovered weeks later.

  • Cloud

    Cloud environments and release pipelines

    AWS accounts in your company’s name, defined as code, released in stages with monitoring and the change history a supplier review will ask you to produce.

Cost


How much does custom software development cost in Bristol?

Custom software for a Bristol company is priced on the scope of the first release, the systems it connects to and the evidence it must produce for a certification body or a data protection review, not on headcount. QalbIT’s fixed-scope work starts from $5,000, which covers a scoped first version, and is invoiced in pounds sterling at the rate set in the contract. You get a written scope with the exclusions named within 48 hours of the first call, and most first releases ship 6 to 14 weeks after that scope is signed.

Those floors are ours, and they are the only prices on this page. The ranges published online for Bristol vary tenfold and cite nothing, so we have not added one.

Nor do we print what a Bristol or Bath software house charges: we have no figure we could pin on a named firm. Give the same written scope to three West of England firms and their replies will tell you more than this page can.

We scope before we price: one discovery call, a written scope that names the exclusions, then a fixed phase-one price before you commit to anything past discovery. Test every quote you get, ours included, against the six drivers below.

Try the software development cost calculator

What moves the number

  • What the first release has to do

    This moves the price more than anything else. A certification tracker that handles one product line properly is worth more than four half-built modules, and it makes phase two easier to fund.

  • The systems it connects to

    Connecting to a documented REST API with OAuth is quick. An old quality-management system or a home-grown production database needs a middleware layer and its own reconciliation view.

  • Evidence for certification and data protection reviews

    Audit trails, non-conformance records, retention rules, access reviews and any export-control access limits all take engineering time. Planned from sprint one they are a modest line; added after an audit finding they become a project.

  • Roles and approval chains

    Two kinds of user is a data model. Inspectors, approvers, finance, external auditors and studio freelancers, each with their own sign-off rights, is a system of its own.

  • Platforms and the offline case

    A web app alone, web plus one mobile platform, or web plus iOS and Android working offline: each adds build and test time, and offline use needs conflict handling designed on purpose.

  • How much history moves

    Carrying over live records and open work is routine. Moving a component’s full history, or years of transactions reconciled and approved by finance, gets its own estimate.

How we work with Bristol teams


A custom software development process for Bristol, live every UK morning

Bristol is four and a half hours behind Ahmedabad in British Summer Time and five and a half behind in winter. That puts your morning in our afternoon, and every step below is planned inside that window.

  1. Discovery and written scope

    One call about how the work moves today, who touches it and where it breaks, then a written scope with the exclusions named. The document is yours whatever you decide.

    A scope, a first-phase price range and the name of the engineer who would lead the build.

    48 hours

  2. Prototype and architecture

    Clickable screens in week one, so your operations lead argues with something real. Alongside them: the data model, access control, hosting region and rollback path, agreed in writing before an editor is opened.

    Approved screens, an architecture your technical lead has challenged, a data protection position your compliance lead has seen.

    1 to 2 weeks

  3. Build in two-week slices

    Working software demonstrated every fortnight in your morning, against real records rather than dummy data. Each slice is checked against the scope while you are on the call, so progress is watched rather than reported.

    Working modules proven against real scenarios, and a backlog you have shaped as you went.

    6 to 14 weeks, by scope

  4. Harden, then release

    Permissions, load behaviour, backups, monitoring and a rehearsed rollback signed off before anything reaches a Bristol user. Where an audit trail is required, it is produced here rather than promised.

    A release your security reviewer can sign off, evidence attached rather than described.

    2 to 3 weeks

  5. Run and extend

    Monitoring, a support window that follows UK office hours, and the next slice of roadmap chosen from what people actually use.

    A platform that keeps earning its place, and a team that hands it to yours whenever you ask.

    Monthly, 30 days notice

India keeps one clock all year and Bristol changes twice. From the last Sunday in October to the last Sunday in March, 09:00 in Bristol is 14:30 in Ahmedabad; for the rest of the year it is 13:30. Our live window is 09:00 to 13:30 UK time in winter and 09:00 to 14:30 in summer: stand-ups, demos and decisions sit inside it, and a written handover goes out before we close.

Book a scoping call

Where we fit


Bristol projects that work well from a distance

These are the engagements a remote team handles well. The ones that need people on site or a UK-established supplier are listed higher up the page, and we mean that list.

  • First build

    Replacing the spreadsheet that runs the operation

    Certification tracking, production scheduling or client records held together by a shared drive and one person who knows the workarounds, rebuilt as a system with roles, approvals and a history of who did what. For operations and quality teams at engineering and creative companies.

  • Rebuild

    Retiring a system the vendor no longer supports

    An old desktop tool or an early web application rebuilt as a maintainable platform, without losing years of records or retraining a team over a weekend. For companies whose core system has outlived its maker.

  • Data protection

    Bringing a system up to UK GDPR properly

    Adding subject access tooling, retention enforcement, deletion that reaches backups and an audit trail that cannot be edited to a platform built before anyone asked for them. A supplier audit or a new compliance lead is usually the trigger. For teams facing a data protection review or a client audit.

  • Extension

    Building around the system of record

    Portals, dashboards and custom modules layered on an ERP, a quality-management system or a production tool, so the core stays put and the retyping around it disappears. For companies extending rather than replacing a core system.

Industries


Sectors we build custom software for in Bristol

Operational software takes the shape of the industry it runs in. These are the Bristol sectors where the process knowledge transfers and the compliance questions are ones we have already answered.

  • Aerospace and advanced engineering

    Certification tracking, non-conformance capture and supplier qualification for suppliers into aerospace and advanced-engineering programmes around Filton, where a component has to be traceable back through its full production history, not just its last inspection.

  • Semiconductor and deep tech

    Internal tooling, data pipelines and test-result tracking for the chip-design and deep-tech companies in the Bristol and Bath corridor, where the software often has to keep pace with hardware that changes every few months.

  • Financial services and fintech

    Client portals, reporting tooling and operations systems for financial-services and fintech firms based in the city, with approval chains, segregation of duties and a complete audit trail shaping the build, and card data kept out of the codebase entirely by tokenising at the processor.

  • Media, animation and games

    Production-asset tracking, scheduling and rights-management tooling for the animation, broadcast and games studios clustered around the harbourside, where a project moves through dozens of contributors and the record of who touched what has to stay intact.

  • Higher education and research spin-outs

    Internal tools, data pipelines and the first commercial platform a research group builds when something it made for itself turns out to be worth selling, for teams around the University of Bristol and the University of the West of England.

  • Renewable energy and maritime

    Monitoring, reporting and supplier-coordination tooling for the renewable-energy and maritime operators working out of the port, where a reading missed or a maintenance window mishandled is a safety question, not just an operational one.

Not on the list? The opening question stays the same: what does a day of this work look like, and where does it break first?

Next step


When the off-the-shelf package stops fitting, that is usually where a custom build starts.

Describe the process the packaged tool cannot follow and we will tell you honestly whether it justifies a build, or whether configuring what you already have would do the job.

UK compliance


Custom software development in Bristol: UK GDPR, engineering evidence and payments

These are the rules that shape how software gets built for a Bristol company, and the questions a supplier outside the country has to answer before anyone signs. We are engineers rather than solicitors: this section describes what we build, and your own counsel and compliance lead decide what applies to you.

  1. UK GDPR and the Data Protection Act 2018

    Any Bristol system holding personal data, whether that is client records, employee data or user information, sits under the UK General Data Protection Regulation and the Data Protection Act 2018, enforced by the Information Commissioner’s Office. The principles that reach the code are lawful basis, purpose limitation, data minimisation, storage limitation, integrity and confidentiality, and accountability, alongside the rights of access, rectification, erasure, restriction, portability and objection. The Data (Use and Access) Act 2025 amends parts of this regime in stages, so the position is re-verified before each publish. In practice that means a data inventory matching what the system actually stores, retention enforced by the system rather than remembered, deletion that reaches backups and exports, subject access answered from the system within the statutory period, and an audit trail that records who read a record as well as who changed it. Lawful basis and whether a data protection impact assessment is needed are decisions for your own data protection lead and counsel. What we build is the machinery that lets you act on the decisions they make. Sources: UK GDPR · Data Protection Act 2018 · Data (Use and Access) Act 2025 · Information Commissioner’s Office.

    Personal data

  2. Traceability and certification evidence for engineering suppliers

    Aerospace suppliers usually work to the AS9100 series, the IAQG’s quality management standard for aviation, space and defence organisations, and their customers expect traceable evidence on request: batch and component tracking, non-conformance records, corrective-action history and supplier qualification files that can be pulled on request rather than assembled from memory during an audit. We build that evidence into the data model from the first sprint, versioned rather than editable in place, with a reason captured at the point a record changes. Certification and the standard your customer requires belong to your quality function, not to us. We build to produce the evidence your auditors ask for, and your team decides when the position is ready to submit. Sources: IAQG 9100-series standards · customer-specific supplier quality requirements, verified per programme.

    Aerospace

  3. UK export controls on technical data

    Defence and dual-use. Some aerospace and defence work around Filton involves technology on the UK’s strategic export control lists. Under UK guidance, letting someone overseas reach controlled technology counts as a transfer even when the server sits in the UK and the files are encrypted, and that transfer needs a licence from the Export Control Joint Unit. Compliance rests with the company that owns the technology, not with its cloud provider. So before any build we ask what the system will hold. Where controlled drawings, specifications or test data are in scope, either the system is designed so our engineers work on the software without ever seeing that data, or we say plainly that the work needs a UK-based team. Classifying your technology, and deciding whether a licence is needed, belong to your export compliance lead. We do not give export-control advice; we design access so the decision they make can be enforced. Sources: GOV.UK, Export of technology, remote access and the use of cloud computing services · Export Control Joint Unit.

  4. PCI DSS, kept out of your codebase

    The simplest way to handle card data is never to hold it. We tokenise at the payment provider, so the card number is captured by the provider’s own hosted field or SDK and your platform stores a token, the last four digits and a scheme. Your application never sees a primary account number, which keeps most of PCI DSS scope out of the code we write. Your PCI obligations stay with your company, and the self-assessment questionnaire depends on how you take payments. We build to keep the scope small and flag any requested feature that would widen it. Sources: PCI DSS v4.0.1 · PCI Security Standards Council.

    Payments

  5. Supplier due-diligence questionnaires

    Engineering suppliers and financial-services firms in Bristol increasingly send a supplier questionnaire before signing, particularly where their own customers or regulators run vendor-risk programmes. We complete it ourselves rather than sending a brochure, describing what we operate: named access with least privilege, review-gated change management, environment separation, logging and retention, tested restores, staged releases and a documented offboarding step. Where the honest answer is no, it is written as no with the compensating control next to it. Where your policy asks for a specific certification from the supplier itself, raise it on the first call and you will get our current position plainly, including where we fall short. Sources: AICPA Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality and Privacy.

    Vendor risk

We build systems that produce this evidence natively rather than adding a compliance module to software that resists it. Where an audit finding or a client deadline is driving your timeline, that date is where we start planning backwards from.

Working with us


Contracting a supplier outside the United Kingdom from Bristol

Legal, finance and whoever holds data protection duties on your side will each have a short list of questions about a supplier outside the country. Most vendor sites leave that list off entirely. Here is ours, with the answers.

  • The contract

    A master services agreement and statement of work governed by English law, with the jurisdiction, liability and termination clauses your counsel prefers. We never ask a Bristol buyer to sign under Indian law, and we never run a project on an exchange of emails instead of a contract.

    English law

  • Currency, VAT and invoicing

    Invoices are raised in pounds sterling against the milestones or the monthly rate fixed in the contract. We are a supplier outside the UK, so VAT treatment is a matter for your accountant, and we provide whatever supplier details your finance team needs to record it correctly.

    GBP

  • Data protection terms

    Where we process personal data on your behalf we sign your processor terms, and any transfer position for a supplier in India is agreed with whoever holds data protection duties on your side before any data moves. Where the work can be done on masked or synthetic data instead, we say so, because it removes the question entirely.

    Article 28

  • Intellectual property

    Code, designs, documentation and infrastructure definitions are assigned to your company as they are created, not on final payment. Repositories, cloud accounts and domains are opened in your name from the first commit.

    Assignment

  • Confidentiality

    A mutual non-disclosure agreement, on your template or ours, is signed before anything confidential is shared. Nothing about your project is used as a reference without written permission.

    NDA

  • Insurance and vetting

    Certificates of insurance are provided on request, and due-diligence questionnaires are completed by the engineers who would do the work. Background checks on named engineers are arranged through your process where your policy requires them; raise it at contract stage rather than at kick-off.

    Due diligence

  • What the lack of a UK entity rules out

    There is no QalbIT entity in the United Kingdom, no Bristol office and nobody we can send to your site on short notice. Where a framework agreement, an export-control condition or a client’s own terms require a UK-established supplier or on-site delivery, we are simply not eligible, and we say so on the first call rather than after a proposal has gone out.

    The limit

None of that argues against a remote partner. It argues for handling the paperwork properly at the start, which is why we raise every item on this list before the estimate rather than after a signature.

Tech stack


Technology behind the custom software we build for Bristol

A certification tracker or a production tool stays in service for years after it ships, so we choose tools a new engineer can read in an afternoon and a future in-house team can maintain without us.

  • Backend and business rules

    • Laravel on PHP 8 for modular business systems with a complete audit trail.
    • Node.js and NestJS where integrations and event-driven flows dominate.
    • Queues, schedulers and retries for syncs, alerts and end-of-day reports.
  • Interface

    • React and Next.js, rendered on the server where search traffic counts.
    • Keyboard-first data entry for certification and production-tracking screens.
    • Flutter for a single iOS and Android codebase that works offline first.
  • Data and integration

    • PostgreSQL and MySQL with constraints that protect record integrity.
    • Append-only audit trails and versioned records where evidence is demanded.
    • REST and GraphQL connections to ERPs, quality systems and payment providers.
  • Security and delivery

    • AWS in your name, in a UK region, defined in Terraform.
    • Logged least-privilege access, with any break-glass use reviewed after the fact.
    • GitHub Actions pipelines with staged, reversible releases.

Already running a quality-management system, a legacy .NET application or a bespoke production database nobody wants to replace? We build around it and write down, before the first sprint, which parts stay exactly where they are.

Outcomes


What custom software should change for a Bristol company

No forecasts. Each row pairs a change the build should make at a Bristol supplier, studio or fintech with the measure that would show it happened.

What custom software should change for a Bristol company: what changes and how you would measure it
What changesHow you would know
One record of the truth across teams, sites and systemsGap between the system and a physical or manual count
Work moves without being rekeyed at each deskHand-offs where someone still copies a value by hand
Approvals are enforced by the system rather than rememberedProportion of transactions carrying a complete approval trail
A subject access or audit request is answered from the systemHours to produce a complete access, deletion or audit response
A fault can be traced to the batch or record that caused itTime to identify the records and the accounts involved
Managers see position without asking anyoneMinutes from question to answer
  • A note on sourcing

    A note on sourcing

    This page carries no market statistics: no Bristol salary bands, no agency day rates, no project failure percentages of unknown origin. Every number is ours or a case-study result, with its source named. If one matters to your decision, ask for the evidence and we will send it or withdraw the claim.

Why QalbIT


Why Bristol companies keep a custom software partner they have never visited

  1. The figures we can evidence

    Since 2018 we have delivered 120+ engagements for 50+ clients. Clutch 5.0 from 8 reviews, Google 4.9 from 18, and 100% job success on Upwork, all on public profiles you can check before a first call.

  2. Your morning live with us, on the same clock as the rest of the UK

    We are live with Bristol from 09:00 UK time all year, until 14:30 during British Summer Time and 13:30 in winter: 13:30 to 19:00 in Ahmedabad in summer, 14:30 to 19:00 in winter. Reviews and decisions happen in your morning, and a written handover covers the rest of your afternoon.

  3. We say what we are not

    No Bristol office, no UK staff, no UK entity, and no implied presence anywhere on this site. The compliance and contract sections above exist because we would rather lose a deal at the scoping call than at a supplier audit.

  4. The proposal names the people who build it

    Nothing is subcontracted, and nobody is pulled off your build mid-sprint for another client. The engineers you interview are the ones whose names appear in the commit history.

  5. We will tell you to hire locally

    If the work needs someone in a Filton test cell or on a harbourside sound stage, a Bristol firm is the better hire and the first call says so. It costs us a project and saves you a year.

The biggest difference has been their flexibility and solution-oriented approach. Rather than pointing out problems, they focus on solving them. I genuinely cannot recall hearing them say, ‘This cannot be done.’ No matter how many changes or updates we send their way, even after long working days, they consistently respond positively and find a way forward. What stands out most is that our relationship has evolved beyond a traditional client-supplier setup and feels more like a partnership. QalbIT takes genuine responsibility for the platform’s functionality, and when bugs are identified, they are addressed without hesitation.
Gabriell Summerland, CEO, Bluecircle

FAQs · Custom software development in Bristol


Questions Bristol teams ask before they start

UK hours, UK GDPR, budgets in pounds, the contract and who owns the code, answered the way we would on a call.

Talk to the team
No, and we say so plainly rather than letting the page imply otherwise. Our only office is in Ahmedabad, India, and we work as a remote engineering partner on UK hours. Where part of a job genuinely needs someone on your site, at Filton or anywhere else, tell us early and we will say honestly whether that piece belongs with a local firm instead.
09:00 to 13:30 UK time sits inside our working day in every month of the year, and 09:00 to 14:30 in British Summer Time, which is 14:30 to 19:00 for us in winter and 13:30 to 19:00 in summer. Stand-ups, demos and design reviews happen inside that window on your morning, and a written handover covers whatever runs past it, so nothing waits on us overnight.
We treat UK GDPR and the Data Protection Act 2018 as a design input from the first sprint: a data inventory that matches what the system actually stores, retention rules enforced rather than remembered, deletion that reaches backups, and an audit trail that records who read a record as well as who changed it. We are engineers rather than solicitors, so your own data protection lead decides what applies and we build the product to match it.
You do, from the first commit. Repositories, cloud accounts and domains are opened in your company’s name, intellectual property is assigned as each piece is written rather than on final invoice, and a mutual NDA is signed before anything confidential changes hands.
A master services agreement under English law, invoiced in pounds sterling, with the jurisdiction and liability clauses your counsel prefers. After the first call you get a written scope with the exclusions named within 48 hours; if it fits, a clickable prototype follows in week one and a demo every two weeks after that, and dedicated engagements run monthly with 30 days notice either way.
Yes. We build batch and component tracking, non-conformance capture and supplier qualification records that stay versioned rather than editable in place, so a component’s history can be pulled on request rather than assembled from memory during an audit. Certification itself, and the standard your customer requires, stays with your quality function; we build the system that produces the traceable evidence an auditor asks for.
Yes. That is one of the harder problems in the corridor’s software: internal tooling, data pipelines and test-result tracking that has to keep pace with hardware revisions rather than lag behind them. We scope the first release around whichever test or data workflow is currently the bottleneck, so the tool earns its place before the next hardware cycle makes it stale.
We tokenise at the payment provider, so the card number is captured by the provider’s own hosted field or SDK and your platform only ever stores a token, the last four digits and a scheme. Your application never sees a primary account number, which keeps most of PCI DSS scope out of the code we write. The self-assessment questionnaire and your PCI obligations stay with your company; we build to keep the scope small and flag anything requested that would widen it.
Yes. A project in these studios typically moves through dozens of contributors, so we build the tracking and rights-management layer around who touched an asset and when, with a record that stays intact as work is handed between departments and freelancers. It usually replaces a shared drive and a naming convention nobody fully trusts.
Fixed-scope projects start from about $5,000, a scoped first version included, invoiced in pounds sterling. For Bristol’s engineering and fintech clients the biggest drivers are usually the certification or audit-trail evidence a release has to produce and the systems it has to connect to: a documented REST API is quick work, a legacy quality-management system or production database needs its own middleware and reconciliation view. A written range with the exclusions listed comes back within 48 hours of the first call, free either way.
Bristol and Bath software houses that work with engineering firms build them, and so do remote specialists. QalbIT is one of the remote ones: we build batch and component traceability, non-conformance and supplier-qualification systems for aerospace suppliers from Ahmedabad, India, with no Bristol office. Ask any candidate to show a part’s full history on one screen. Before you shortlist, check that records are versioned so an AS9100 auditor sees every change with its reason, and that the supplier can work without seeing export-controlled drawings if your programme has any.
Studio pipeline teams build many of them in-house, and the rest come from local developers or remote partners. QalbIT builds production scheduling, asset tracking and review tools for animation, broadcast and games studios as a remote team from Ahmedabad, with no Bristol office, usually alongside the scheduling and asset software a studio already licenses. The first release is normally the schedule: each shot or asset, who holds it, what is waiting for review and which delivery date it puts at risk.
Yes, when the audit is of your quality system and the offshore team builds the software that runs it. The auditor examines your company, not your developer, so what counts is the evidence the system produces and the controls on who can reach it. Export-controlled technical data is the exception and needs its own answer. UK guidance treats overseas access to controlled technology as a transfer that needs a licence, even on a UK server, so where such data is in scope we design the system so our engineers never see it, or tell you the work needs a UK team.
Some app developers build only the iOS and Android screens and leave the server side to another supplier; others build both. QalbIT builds both as one remote team from Ahmedabad, with no Bristol office: a Flutter app for iOS and Android plus the API, admin console, database and integrations behind it, so one team answers for the whole system. On our rate card a mobile app runs $9,000 – $26,500 over 8–14 weeks, iOS and Android from one Flutter codebase on your API; the back office is priced from the written scope.

Next step


Let us scope the first release.

Tell us how work moves through your company today, where it stalls, and which date cannot move. We will map it, name the system that earns its place first, and put an honest price range against a phased plan. If a Bristol firm is genuinely the better answer, the reply says so. Within 48 hours: a written scope, exclusions named, yours whether or not you proceed.