Skip to content

Custom software development · Manchester

Bespoke software development in Manchester.

Bespoke software development for Manchester businesses, built remotely from Ahmedabad, India, on UK hours: custom software, mobile apps and integrations for broadcast and media teams near MediaCityUK, fintech scale-ups with a compliance desk to answer to, retailers running fulfilment at speed, and sports organisations turning match and training data into a decision. There is no QalbIT office in Manchester, and this page sets out exactly what that changes.

Manchester’s agency scene is dense, so a remote partner has to earn its place in the comparison. This page shows the mechanics, the UK rules that shape the build and the rows where a firm in the city beats us.

  • 2018

    Building software since

  • 120+

    Projects delivered

  • 4.5h+

    Live overlap, 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 a remote software partner actually does for a Manchester company

QalbIT builds custom software for Manchester companies as a remote engineering partner rather than a local agency. Two constraints shape most Manchester projects: a fast-moving product decision made by people who expect to see working software, not a deck, and a working day that runs on UK time. We design for both, and we work Manchester mornings from Ahmedabad, India.

What separates the options is rarely the code. It is the contract, the hours and who can be in the room.

Manchester has a dense local tech and agency scene, so the comparison is rarely "remote or nothing". It is usually remote-partner-at-a-lower-blended-rate against a local team that can be in the room the same afternoon. Both are real options with real trade-offs.

None of those trade-offs is a reason to stop. All of them have known answers, and all are cheap to settle before a contract and expensive to discover after a launch date has already been announced.

We are the remote option. The rest of this page is the case for and against us, written down before you have to ask for it.

At a glance

  • Core focus

    Custom platforms, SaaS products, mobile apps and integrations

  • Engagements

    First builds · rebuilds of software you have outgrown · module extensions · standing engineering pods

  • Delivery

    Remote from Ahmedabad on UK hours, live 09:00 to 13:30 UK time in winter and to 14:30 in summer, Monday to Friday

  • Manchester position

    No office, no staff, no UK entity. Your paper, English law

  • Ownership

    Repositories, cloud accounts and IP in your name, assigned as the work is created

Definition


Manchester agency vs freelance contractor vs remote engineering partner

All three get quoted against each other on price, although each one buys you something different.

  • Manchester digital agency

    On UK hours all day, able to sit in your building and pitch you a full brand-to-build service. You are buying proximity and breadth. Best when the work is stakeholder-heavy or spans brand, design and build together.

  • Freelance or contract developer

    One person billed into your own process. You are buying capacity, and architecture, code review and release management stay with you or your internal lead. Best when you already have engineering leadership with bandwidth to direct someone.

  • Remote engineering partner

    A small senior team that owns one defined build, a product release or a content tool, and works your morning from Ahmedabad. The repository, the release pipeline and the runbook are yours at the end. With no UK entity, contract, data protection terms and your security questionnaire come first, before any sprint. Best when the product decision is made and it needs building properly.

We sell the third. If an agency or a contractor fits your work better, you hear that on the first call, before any deposit changes hands.

Fit


When a remote partner is the right call for a Manchester company, and when it is not

Two lists with both sides argued, because a Manchester buyer usually has a local quote on the table as well.

  • Hire a remote partner when

    • A product owner on your side can say what the system must do and decide on it the same week.
    • The job has edges, a first release, a rebuild or a set of modules, rather than a programme whose sponsor changes every quarter.
    • Calls, demos and decisions fit inside 09:00 to 13:30 UK time, or 14:30 in summer, and the afternoon can run on a written handover.
    • At the end you want the repository, the release pipeline and the runbook sitting in your own accounts.
    • The build is mostly software and integration work, rather than brand, design and a public launch bundled together.
  • Hire locally instead when

    • Procurement, or a client contract you have already signed, says the supplier must be based in the United Kingdom.
    • The engagement is really a brand-led launch that needs an agency in the room every week for stakeholder workshops.
    • Your security policy rules out production access from outside the UK, and masked data will not do the job.
    • Decisions get made late in the UK day, after a shoot or a match, so someone has to be live until 18:00.
    • What you need is one more developer under your own architect, which a contractor supplies with less overhead.

What that looks like in practice here

Manchester has a mature local tech, fintech and agency scene, so buyers are used to comparing suppliers on more than price. Vendor questionnaires arrive early and a vague answer is noticed. The parts of a remote engagement that worry a reviewer are the parts we settle in writing before the build: access control, where data sits, who can reach production, what is logged, how a release is approved and how it is reversed. We would rather hand your reviewer engineering evidence than a capability deck. Projects on the second list we turn down. Building remotely what a Manchester team should have built in the room costs far more than our fee, and by the third sprint everybody can see it.

Next step


Still deciding between a local team and us?

Send us what the system has to do, what data it will hold and how your stakeholders expect to see progress. We will tell you honestly which list you belong in, including when the answer is "hire someone in the city".

Comparison


Remote partner vs a Manchester agency vs a freelance contractor

Each row is a difference a Manchester buyer will meet, the ones that go against us included. There is no rate row: we hold no sourced figure for what agencies here charge, and a guessed one would mislead you. Send us the real scope, the data it holds and your procurement rules, and we will fill this table in for your case.

A remote engineering partner compared with a Manchester digital agency and a freelance developer, row by row
Manchester digital agencyFreelance or contract developerQalbIT (remote partner)
Office you can walk intoYesSometimesNo
Live hours on UK timeFull working dayFull working day, usually09:00 to 13:30 UK time live (14:30 in summer), a written handover for the rest of the day
Who owns the architectureThe agencyYou doWe do, reviewed with your technical lead
Who owns testing and releaseThe agencyYou doWe do, with your sign-off as the gate
Contract and governing lawDomesticDomesticYour paper, English law, invoiced in pounds sterling
Source code and IPVaries by contractYoursYours, assigned as the work is created
Security and vendor questionnairesRoutineRoutineAnswered by the engineers, insurance certificates on request
Contracts with a work-location clauseEligibleUsually eligibleNot eligible without a domestic supplier
People on your accountMove with agency workloadOne person, availability-dependentA small senior team, named in the proposal, the same people throughout
  • 01

    Read the rows we lose first.

    A table that one supplier wins on every line is marketing. Several rows above are reasons to hire a Manchester firm instead, and they are cheaper to find here than three months into a contract.

  • 02

    A rebrand or a customer launch usually wants an agency.

    Where the work is brand, design and a public launch together, a Manchester agency with people in the room every week genuinely is the stronger fit, and we will say so rather than scope around it.

  • 03

    A single contractor is capacity, not a delivery team.

    One freelance developer is a person added to a process you already run. If nobody on your side is holding architecture, code review and release quality, that capacity produces code faster than it produces a working system.

  • 04

    A work-location clause settles it.

    When a client contract or a procurement rule says the work must be performed in the UK, engineering quality cannot make up for it. Put the clause to us on the first call and you will have the answer that day.

What we build


Custom software we build for Manchester companies

Systems that talk to each other, so a transaction, a booking or a piece of content moves through operations and finance without three people retyping it.

  • Platforms

    Operations platforms and internal systems

    The system that runs the business: intake, approvals, scheduling, exceptions and reporting, built around your process rather than a template.

  • Media

    Media and content operations tooling

    Asset management, scheduling and metadata tooling for broadcast and content teams, built to fit around the systems a production already runs.

  • SaaS

    SaaS products and MVPs

    Multi-tenant products with billing, roles, usage limits and an audit trail, shaped for a founding team that needs paying users before the next raise.

  • Fintech

    Fintech portals and reporting tools

    Onboarding, reconciliation and reporting screens for finance teams, with card data kept out of your systems entirely by tokenising at the processor.

  • Mobile

    Mobile apps for people away from a desk

    One Flutter codebase across iOS and Android for couriers, members and field staff, built offline-first because the signal on a delivery round is not their problem to solve.

  • Integrations

    APIs and integration engineering

    Wiring a payments provider, a CRM or a broadcast system to the tools around it, with queues, retries and a reconciliation view so a failed message is visible rather than silent.

Cost


How much does custom software development cost in Manchester?

Custom software for a Manchester company is priced on scope, integration count and the compliance evidence the system has to produce, not on headcount. At QalbIT, fixed-scope projects start from $5,000, a scoped MVP included, and dedicated engineers from $3,200 per engineer per month. A written scope with the exclusions named comes back within 48 hours of the first call, and a first release usually lands 6-14 weeks after that scope is signed.

Those two floors are the only cost figures on this page. Search the question and you will find ranges a factor of ten apart with nothing behind them, and we would rather not add another.

We also do not publish what a Manchester agency charges, because we have no figure we could attribute to anyone. Ask two or three firms in the city for a quote on the same written scope and you will have better information than any page on this subject can give you.

So we scope before we price: one discovery call, a written scope with the exclusions listed, then a fixed price for phase one before you commit beyond discovery. The drivers below are what move the number; use them to test any quote, ours included.

Try the software development cost calculator

What moves the number

  • Scope of the first release

    The largest single driver, and the one most often got wrong. One workflow built properly beats four built thinly, and a first release that does one job well is far easier to fund a second phase from.

  • Integration count and quality

    Each connected system adds scope, and not equally. A documented REST API with OAuth is straightforward. An older platform with a nightly file export needs a middleware layer and a reconciliation view of its own.

  • Compliance evidence

    Audit trails, consent handling and reporting are engineering work with their own timeline. Designed in at the start they are modest. Retrofitted after a regulator or an investor asks about them, they are a project.

  • Roles and approval rules

    Two user types is a data model. A newsroom or a payments desk with editors, approvers, maker-checker rules and delegated sign-off is a system of its own, and it is where operations software quietly grows.

  • Platform count

    Web alone, web plus one app, or web plus iOS and Android working offline on a matchday or a delivery round: every step adds build, test and release work.

  • Data migration depth

    Moving current records is routine. Moving years of transactional history, reconciled against the old system, is a workstream that deserves its own estimate.

How we work with Manchester teams


A delivery process built around a 4.5 to 5.5-hour offset

The offset is real, so the plan works with it. 09:00 in Manchester is early afternoon in Ahmedabad, and every stand-up, demo and decision call is booked inside the hours we share.

  1. Discovery and written scope

    One call to walk through how work moves through your product or your operation today, who touches it and where it breaks, then a written scope with the exclusions named. The document is yours whether or not you hire us.

    A written scope, a price range for phase one and the engineer who would lead it, by name.

    48 hours

  2. Prototype and architecture

    A clickable prototype in week one, so your product or operations lead argues with real screens instead of a requirements document. Alongside it: the data model, access control and hosting region, agreed in writing before anyone opens an editor.

    Approved screens and an architecture your CTO or technical adviser can read.

    1-2 weeks

  3. Build in fortnightly slices

    Working software demoed every two weeks, live in your morning, against real data rather than dummy data. Each slice is checked against the scope in front of you.

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

    6-14 weeks, scope-dependent

  4. Harden, then release

    Permissions, load, backups, monitoring and a rehearsed rollback are signed off before your users or your audience see anything.

    A release your security or compliance reviewer can accept, with the evidence attached rather than described.

    2-3 weeks

  5. Run and extend

    Monitoring, support across UK hours, and the next slice of roadmap picked from what your users actually do.

    A platform that keeps paying its way, and a handover to your own team whenever you want one.

    Monthly, 30 days notice

In British Summer Time, from the last Sunday in March to the last Sunday in October, Ahmedabad is four and a half hours ahead of Manchester; in winter it is five and a half, because India keeps one clock all year. A 09:00 stand-up on a matchday morning is 13:30 or 14:30 for us. Demos and decision calls sit in your morning, and a written handover goes out before our day closes.

Book a scoping call

Where we fit best


Manchester projects we take on

Engagements that run well at a distance. The ones that need people in a Salford studio or in your office are on the second list above, and we mean that list.

  • First build

    Replacing the spreadsheet that runs the company

    Operations held together by workbooks, a shared inbox and one person who knows the exceptions, rebuilt as a system with roles, approvals and a history of who did what. For operations, finance and content teams at growing companies.

  • Modernisation

    Rebuilding software you have outgrown

    An early web application or a legacy platform rebuilt as a maintainable product, without losing a decade of data or retraining everybody in a weekend. For teams on a platform its maker no longer supports.

  • MVP

    A first product that has to win a paying customer

    A scoped first version, one platform and the core journey, with a clickable prototype in week one and a live demo every two weeks after that. For founders who need traction before the next funding conversation.

  • Extension

    Extending what you already own

    Custom modules, portals, dashboards and integrations layered on top of a CRM, a payments platform or a broadcast system, so you keep the system of record and lose the retyping around it. For teams keeping the core system and losing the retyping.

Industries


Sectors we build for in Manchester

Each of these sectors runs on its own clock, its own data and its own rules. These are the Manchester ones where we already know all three.

  1. Media, broadcast and content

    Asset management, scheduling and metadata tooling for teams around MediaCityUK in Salford, home to the BBC, ITV and the dock10 studios. Rights windows and delivery deadlines drive the workflow, and on Ofcom-licensed channels so do subtitling, audio description and signing, so the data model has to show which version of a programme carries which access file and whether it is cleared.

  2. Fintech and financial services

    Onboarding, reconciliation and reporting tools for Manchester fintech scale-ups and payments businesses, with approval chains, an audit trail and card data kept off your systems entirely by tokenising at the processor. Where the firm is FCA-authorised, the outsourcing rules in the compliance section below decide how we document what we run.

  3. Retail and e-commerce

    Order, inventory and fulfilment systems for retailers whose online channel now moves as much stock as a store once did, integrated with the warehouse and carrier systems behind it.

  4. Sport and sports technology

    Data and reporting tools for clubs and sports organisations turning match, training and ticketing data into a decision a coach or a commercial team can act on, rather than a spreadsheet nobody opens twice. Injury and medical records are health data under UK GDPR, so they sit behind their own access rules, apart from the scouting and commercial data around them.

  5. Professional and legal services

    Case and matter management, client portals and reporting for firms whose growth has outpaced a shared inbox, with the access controls a client review now expects.

  6. Higher education and research

    Internal tools, data pipelines and the first commercial platform a university spin-out builds when a tool made for itself turns out to be worth extending for others.

Sector not listed? The first question stays the same: what does a normal day of this work look like, and where does it go wrong?

Next step


Your process is the reason the off-the-shelf product does not fit.

Tell us the step the packaged product cannot follow, a rights check, a reconciliation or a fixture change, and we will say whether it justifies a build or whether configuring what you already own would do.

Manchester compliance


Building software for Manchester: data, payments and third-party oversight

These are the obligations that decide how a system is built for a Manchester business, and the questions a supplier outside the country has to answer before you sign anything. We are engineers and not your counsel: what follows is what we build, not legal advice about what applies to you.

  1. UK GDPR and the Data Protection Act 2018

    Personal data a Manchester business holds falls under UK GDPR and the Data Protection Act 2018, and the Information Commissioner’s Office enforces both. The duties that reach the code are a lawful basis for each use, data minimisation, the rights of access, correction and erasure, and reporting a qualifying breach to the ICO within 72 hours of becoming aware of it. Some Manchester systems hold more than ordinary personal data. A club’s injury and medical records are data concerning health, one of the special categories, and need a separate condition for processing and tighter access than the scouting or ticketing data beside them. We build that separation into the data model rather than leaving it to a permission setting someone can change. Your DPO or counsel decides the lawful basis, the special-category condition and whether an impact assessment is needed. We build the inventory, the request workflows, the access separation and the logs that let you show it. Sources: UK GDPR Articles 6, 9 and 33 · Data Protection Act 2018 · ICO guidance on special category data.

    General

  2. FCA-regulated firms and third-party oversight

    An FCA-authorised Manchester firm using an outsourced software supplier is expected to maintain oversight of that arrangement under the FCA's outsourcing and operational resilience rules: a documented understanding of what the supplier does, tested continuity arrangements, and the ability to exit the arrangement without disrupting the business. Payments firms have a further step. Under regulation 25 of the Payment Services Regulations 2017, an authorised payment institution tells the FCA before it outsources an operational function of its payment services, and an important one, IT systems included, must not be outsourced in a way that weakens its internal control or the FCA’s ability to supervise it. We support that with a written description of what we run, tested backup and restore, staged releases with rollback, and monitoring your operations team can see directly rather than take on trust. Whether an arrangement is material outsourcing, and what your firm must record or notify to the FCA, is for your compliance function to decide. We produce the operational evidence behind that decision. Sources: FCA SYSC 8 (Outsourcing) · FCA Operational Resilience Policy Statement PS21/3 · Payment Services Regulations 2017, regulation 25.

    Financial services

  3. Ofcom access services and broadcast deliverables

    Channels Ofcom lists under its Code on Television Access Services carry subtitling, audio description and signing duties, and programme guides flag which programmes have them. For content tooling that becomes data: each version of a programme linked to its subtitle, audio description and signed files, the access flags a guide needs, and a report the compliance team can run without rebuilding a spreadsheet. Which channels and targets apply, and how they are reported, is for your compliance team under Ofcom’s code. We build the asset and metadata system that holds the evidence. Sources: Ofcom Code on Television Access Services · Ofcom.

    Broadcast

  4. PCI DSS, kept off your checkout and ticketing code

    Card data is safest when your systems never hold it. For a retailer’s checkout or a club’s ticketing and membership renewals we tokenise at the processor: the card number goes into the processor’s hosted field, and your platform keeps a token, the last four digits and the card brand. No primary account number passes through the code we write, which keeps most of PCI DSS out of scope. PCI DSS obligations stay with your business, and the self-assessment questionnaire you file follows from how you take payments. We keep the scope small and flag a feature that would widen it before it is built. Sources: PCI DSS v4.0.1 · PCI Security Standards Council.

    Payments

  5. SOC 2 vendor questionnaires

    Most Manchester buyers of any size will send a vendor security questionnaire before a contract is signed. We complete it ourselves rather than returning a brochure, and we answer with what we operate: named access with least privilege, change management through pull request and review, environment separation, logging and retention, tested backups, staged releases and a documented offboarding step when an engineer rolls off. If the honest answer is no, the questionnaire says no and names the compensating control. Padding is easy to spot, and it is how a supplier drops off a shortlist at the last stage. Where your policy needs an attestation report from the supplier itself, say so on the first call and you will get our current position in plain words. 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 bolting a compliance module onto software that resists it. Where a regulatory deadline or an investor review is driving your timeline, that date is where we start planning backwards from.

Working with us


Hiring a vendor outside the United Kingdom: the honest version

Your legal, finance and compliance teams will each have a short list of questions about a supplier outside the country. Most vendors leave those lists off the website. Here is ours, with the answers.

  • The contract

    Your master services agreement, under English law, with the jurisdiction, liability and termination clauses your counsel asks for. We never ask a Manchester client to contract under another country’s law, and we never run a build on an exchange of emails.

    Governing law

  • Tax paperwork and invoicing

    QalbIT is not a UK business. Invoices go out in pounds sterling against the milestones or the monthly rate in the contract, each carrying your purchase order reference. How VAT applies to a supply from outside the UK is for your accountant to confirm.

    Invoicing

  • Intellectual property

    Code, designs, documentation and infrastructure definitions become yours as each is created, not when the last invoice is paid. Repositories, cloud accounts and domains are opened in your company’s name from the first commit, so nothing has to be transferred at the end.

    Assignment

  • Confidentiality

    A mutual NDA, on your template or ours, is signed before anything sensitive changes hands, whether that is a product roadmap or a format still in development. We never name you or your project as a reference without your written agreement.

    NDA

  • Insurance and security questionnaires

    Insurance certificates on request. Security questionnaires are filled in by the engineers who would do the work, not a sales team, and the answers describe what we run today.

    Vendor risk

  • No local entity, and what that rules out

    QalbIT has no UK entity, no Manchester office and nobody who can be in your building on Tuesday. Where a procurement rule or a client contract requires a domestic supplier or work performed in the UK, we are not eligible, and you will hear that on the first call rather than after a proposal.

    The limit

The list is not a case against hiring remotely. It is the paperwork a remote build needs, so we put it on the table during scoping rather than leaving it for your legal review to find.

Tech stack


Technology we use for Manchester builds

Business systems live for a decade, so we choose technology a new engineer can read in an afternoon and your future team, internal or not, can maintain without us.

  • Backend and business logic

    • Laravel (PHP 8) for modular business systems with strong audit trails.
    • Node.js and NestJS where integrations and event-driven flows dominate.
    • Queues, schedulers and retries for syncs, alerts and report generation.
  • Interface and usability

    • Next.js and React, server-rendered where search traffic matters.
    • Keyboard-first data entry for screens people live in all day.
    • Flutter for one mobile codebase across iOS and Android, offline-first.
  • Data and integrations

    • PostgreSQL and MySQL with constraints that protect financial integrity.
    • Versioned records and append-only audit trails where evidence is required.
    • REST and GraphQL integrations with CRMs, processors and content systems.
  • Security and delivery

    • AWS accounts in your name, defined in Terraform rather than by hand.
    • Least-privilege access, logged, with break-glass reviewed after use.
    • Staged releases through GitHub Actions, every one reversible.

Already running a bespoke .NET system, a legacy PHP platform or a payments integration nobody wants to touch? We extend what works and put in writing, before any code is written, which parts should be left exactly where they are.

Outcomes


What the project should actually change

Changes you can check, not projections: what the build should alter in a working week, and the number that would show it did.

What the project should actually change: what changes and how you would measure it
What changesHow you would measure it
One record of the truth across sites and systemsVariance between the system and a manual count
Content, orders and payments move without being retypedHand-offs where a person still copies a value across
Approvals are enforced rather than rememberedShare of transactions with a complete approval trail
Vendor and compliance requests are answered from the systemHours to produce an access or audit response
Incidents can be scoped preciselyTime to establish which records were reached, and by whom
Producers and managers see the position without asking anyoneTime from question to answer
  • A note on sourcing

    A note on sourcing

    This page quotes no market data. Salary bands, agency rates and the failure statistics passed around without a primary study are all missing on purpose. The figures that are here are QalbIT’s own and each names its source; ask for any of them and we will send the evidence or withdraw the claim.

Why QalbIT


Why Manchester companies keep us on the project

  1. Since 2018, with figures you can check

    Since 2018 we have delivered 120+ engagements for 50+ clients across web, mobile and platform work. On public profiles: Clutch 5.0 from 8 reviews, Google 4.9 from 18 reviews and 100% job success on Upwork. Those are the figures we can evidence, so they are the only ones we quote.

  2. Your mornings, live

    Four and a half to five and a half live hours every working day, 09:00 to 13:30 UK time in winter and to 14:30 in summer. Stand-ups, demos and decisions happen inside them, and a written handover reaches you before our day ends, so nothing waits for a status meeting.

  3. We say what we are

    No Manchester office, no UK staff, no United Kingdom entity and no implied presence anywhere on this site. The compliance and paperwork sections exist because we would rather lose a deal at the scoping call than at a vendor review.

  4. The people in the proposal write the code

    The engineers named in the proposal are the ones on the commits. Nothing is passed to another firm, nobody is swapped out mid-sprint, and the founder is reachable without an account manager in between.

  5. When a local agency is the better call, we say so

    When a Manchester agency is genuinely the better answer, for example a brand-led launch that needs people in the room every week, you hear it on the first call. 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 Manchester


Questions Manchester teams ask before they start

UK-hours cover, budgets, third-party oversight and who owns what, answered the way we would answer them on a call.

Talk to the team
No, and we will not pretend otherwise. Our only office is in Ahmedabad, India, and we work as a remote engineering partner on UK hours. If part of the job needs someone physically in your building, tell us early and we will say honestly whether that part belongs with a local firm.
Yes. 09:00 to 13:30 UK time sits inside our working day every month of the year, and 09:00 to 14:30 in British Summer Time, which is 14:30 to 19:00 IST in winter and 13:30 to 19:00 IST in summer. Stand-ups, demos and design reviews all sit inside that window, and a written handover goes out before our day closes.
Fixed-scope projects start from about $5,000, a scoped MVP included, and dedicated engineers from $3,200 per engineer per month, invoiced in pounds sterling. Where your project lands depends on user roles, integrations and how many platforms it has to run on. You get a written range with the exclusions listed within 48 hours of the first call, free either way.
We treat UK GDPR and the Data Protection Act 2018 as a design consideration from the first sprint: a data inventory, retention rules a person can actually read, subject access and deletion workflows, and an audit trail that records who read a record as well as who changed it. We are engineers rather than your solicitors, so your own data protection lead decides what applies and we build the product to match it.
Yes. We provide a written description of what we run for your third-party register, tested backup and restore, staged releases with rollback, and monitoring your operations team can see directly. Whether an arrangement is material outsourcing, and what your firm must record or notify to the FCA, is for your compliance function to decide.
Manchester keeps the same clock as the rest of the UK, so we are four and a half hours ahead of you in British Summer Time and five and a half in winter, since India does not observe daylight saving. Your whole morning falls inside our working day: 09:00 to 13:30 UK time in winter and 09:00 to 14:30 in summer.
You do, from the first commit. Repositories, cloud accounts and domains are created in your company’s name, intellectual property is assigned as the work is created rather than on final payment, and an NDA is in place before you share anything sensitive.
Yes, including asset management, scheduling and metadata tooling built to fit around the systems a production already runs. Rights and delivery deadlines usually drive the workflow, so the data model is built to make a piece of content findable and its clearance status obvious.
Yes. We build onboarding flows, reconciliation and reporting tools, customer portals and the integrations to a payments provider or a banking API, with approval chains and an audit trail designed in. Card data stays with the processor through tokenisation. We work remotely from Ahmedabad on UK hours, and the code sits in your company’s name from the first commit. If you are an authorised payment institution, the Payment Services Regulations 2017 have you tell the FCA before outsourcing an operational function, so we supply the written description of what we run that your notification and your oversight need.
We can, as a remote team: asset and version tracking, rights windows, scheduling, metadata, and the link between each programme and its subtitle, audio description and signed files, built around the systems a production already runs. There is no QalbIT office in Salford or Manchester, so anything that needs a person in a studio belongs with a local firm. A first release is usually one workflow, such as clearance or deliverables tracking, scoped in writing within 48 hours of the first call and demonstrated every fortnight in your morning.
Not the whole day, and we would rather say so up front. We are live from 09:00 UK time every working day until 13:30 in winter and 14:30 in summer, four and a half to five and a half hours. Stand-ups, demos and decisions sit in that window, and a written handover covers the rest of your afternoon so nothing waits overnight for an answer you needed. If the people who decide are only free late in the day, after a shoot or a match, a team in the city on your clock all day may suit you better, and we will tell you that on the first call.
You contract with QalbIT Infotech, an Indian company, and we sign your master services agreement under English law with the jurisdiction, liability and termination clauses your counsel prefers. We do not ask clients to contract under the law of another country. Invoices are raised in pounds sterling against the milestones in the contract.
One discovery call, then a written scope with the exclusions named, back inside 48 hours. If it fits, a clickable prototype follows in week one and a demo every two weeks after that. Dedicated engagements run monthly with 30 days notice on either side, so nothing locks you in while you are still deciding.

Next step


Let us scope the first release.

Tell us how work moves through your business 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 Manchester firm is the better answer, that is what the reply will say. Inside 48 hours: a written scope with the exclusions named, and it is yours whether or not we build it.