Founder

Dr Zaid Ismail

Practising NHS GP, builder of airGP, and self-taught programmer.

airGP was created to solve a practical problem: too much fragmented admin for locum work and not enough purpose-built software for NHS primary care.

I build tools that are useful, simple, and cost-effective for both general practitioners and organisations.

Practising NHS GP
Self-taught developer
Built for NHS primary care
GMC 7040881
Portrait of Dr Zaid Ismail

Building practical software for locum workflows, pensions, and invoicing.

Why I built airGP

I built airGP because I was spending too much time managing the administrative side of locum work.

Like many GP locums, I found myself using a combination of spreadsheets, emails, Word documents, PDF invoices, and calendar entries to keep track of sessions, payments, pensions, and tax records. It worked, but it was time-consuming and prone to mistakes.

I wanted a simple system that would allow me to manage everything in one place, specifically designed for how GP locums actually work. I found other platforms were either complicated, outdated, or missing certain features.

My GP locum experience

Practising NHS GP with experience across general practice, extended access services, and federation-led services.

Built from first-hand experience managing multiple practices, different rates of pay, invoices, pensions, and tax records.

Product direction continues to be shaped by real GP locum workflows and feedback from practising GP locums.

Problems I personally experienced

I found that much of this work was repetitive and administrative rather than clinical.

Keeping track of sessions worked across multiple organisations.

Remembering which invoices had been sent and which had been paid.

Managing NHS pension records and PCSE logging.

Preparing information for tax returns.

Finding historical invoices and payment records.

Tracking expenses and income throughout the year.

Maintaining accurate records for accountants.

Why existing solutions did not work for me

I wanted something that reflected the actual workflow of a GP locum, from booking a session through to invoicing, pension administration, and tax reporting.

Too generic and not designed specifically for GP locums.

Focused mainly on booking shifts rather than the wider locum workflow.

Expensive for individual locums.

Missing pension tracking functionality.

Missing tax and reporting tools.

Difficult to use day to day.

How airGP evolved

airGP began as a simple session and invoice tracker. Over time, feedback from users helped shape the platform into a more complete locum management system.

Session management
Invoice generation
Payment tracking
NHS pension tracking
Pension reminders
Payment reminder emails
Property income tracking
Making Tax Digital exports
Invoice email logs
Referral functionality

Commitment to data security

As a practising GP, I understand the importance of confidentiality, security, and professional responsibility. airGP is designed to store only the information necessary to provide the service and takes a security-first approach to development.

  • Encrypted connections using HTTPS.
  • Secure authentication and access controls.
  • Regular software updates.
  • Secure UK and EU cloud infrastructure providers.
  • Data minimisation principles wherever possible.

Looking ahead

The goal of airGP remains simple: reduce administrative burden for GP locums so they can spend less time on paperwork and more time on patient care.

  • Improved pension workflows.
  • Enhanced tax reporting tools.
  • Additional Making Tax Digital functionality.
  • Better practice and organisation management features.
  • Further automation of common locum administrative tasks.
  • New integrations that simplify day-to-day workflows.