Capability statement

01Company

Legal name

Prosperly Limited

Trading names

Prosperly, Surgerly

Company number

15988727, registered in England and Wales

Incorporated

1 October 2024

Nature of business

SIC 62020, information technology consultancy

Organisation size

SME

Data protection

Registered with the ICO, reference ZB949427

Hosting

Microsoft Azure, UK South

Led by

Dr Daniel Howard MB BChir, Director

Contact

enquiries@prosperly.co.uk

02What we do

We design, build and run software for healthcare, and the change that goes with it: from discovery and process redesign to production software, data migration and the cloud infrastructure underneath.

• Transformation

  Mapping how an organisation really works, then redesigning it around one record and one way of working, with the people who do the work.

• Product engineering

  Web platforms designed, built and run end to end, including Surgerly, our flagship electronic patient record.

• Data migration

  Moving records, notes and files off legacy systems with old and new running side by side, so nobody has to stop working on a cut-over day.

• Integration

  Connecting the systems organisations keep: CRM, telephony, card payments, SMS, email marketing, and Microsoft 365 with Entra ID single sign-on.

• Cloud & security engineering

  Isolated installations on Microsoft Azure in the UK, each with its own network, database, secrets and encryption keys, provisioned by script so every one is built the same way.

• Automation

  Configurable workflows for reminders, confirmations, follow-ups and tasks, so teams change the process without waiting for a release.

• Patient-facing experience

  Booking forms embedded in an organisation’s own website, patient portals on its own domain, and messages in its own voice.

• Data & reporting

  Scheduled pipelines that bring practice-management, CRM, advertising, analytics and finance data together in one database, ready for reporting and dashboards.

03Flagship product

04Experience

Our work is in production with private healthcare providers including Transform, Signature Clinic, La Belle Forme and Electiva. It includes:

• a separate cloud installation of Surgerly for each company, built and run from a repeatable, scripted provisioning process;
• moves onto Surgerly from legacy practice-management systems, with old and new running side by side until each team is ready to switch;
• connections to CRM, telephony, card payments, SMS and email marketing, and Microsoft 365 single sign-on for staff;
• booking forms embedded in providers’ own websites, so enquiries arrive in the patient record with the brand’s own look;
• SMS appointment reminders with reply-to-confirm, and a governance pilot for incidents, complaints and risk with real users;
• data pipelines that bring practice-management, CRM, advertising, web analytics and finance data together for reporting and dashboards;
• a secure, read-only view of practitioner availability for a clinic’s partners, with one-time-code sign-in, built and live within a day.

Case studies, with dated figures

05How we build

Software that is safe to change, by habit rather than heroics. This is how Surgerly is built and released today.

• Tested continuously

  Automated unit, contract and integration tests. A core suite runs on every change, the full suite runs every night, and every deployment is smoke-tested.

• Security in the pipeline

  Static security analysis, dependency vulnerability checks and secret scanning on every change. Each build records a software bill of materials, and third-party code is pinned to exact versions.

• Staged releases

  Changes move from development to UAT to production one stage at a time. Production only receives builds that have already deployed cleanly to UAT, and only a named owner can release to it.

• Versioned data changes

  Every database change is numbered, fingerprinted once applied, and shipped with its own undo script.

• Infrastructure by script

  Every installation is built by the same phased provisioning scripts, with automated checks for drift between installations and between stages.

• No stored deploy passwords

  Deployments sign in to Azure without stored credentials.

• Rehearsed migrations

  Data moves are rehearsed end to end, verified before go-live and reversible: a snapshot comes first, and protected data is re-encrypted under the new installation’s own keys.

• Monitored

  Central logging, with alerts on errors and failed background jobs.

06Assurance

What we have in place today, and how we keep raising the bar.