Skip to content

About

A specialist-led software agency.

Each practice at Carpediemsoft is run by an engineer who has shipped that kind of system in production, and the lead who scopes your project stays on it until it is running.

Our story

Why Carpediemsoft exists

Most growing companies do not need a large vendor. They need a few experienced people who can own a problem end to end, say clearly what they will and will not do, and still be there when the system is in production. Carpediemsoft is built to work that way.

Each practice is led by someone who has done that kind of work in production, and a practice gets a page on this site only when it has a lead and proof. Our backend practice, for example, is led by an engineer who owned core subsystems of a multi-tenant care-coordination platform used by hospital systems.

One company, one point of accountability. The practice lead who scopes your work is the one who delivers it, and one owner is accountable for every engagement. We write down decisions, show our work in progress, and treat tenancy, security and data correctness as structural properties of a system rather than things to check later. If a project is not a fit, we will say so early.

How we’re organized

Each practice has a named lead who scopes and builds the work. A practice gets a page only when it has a lead and proof.

Who we are

The people accountable for the work

  • Muhammad Tahir Hassan Khan

    Backend Software Engineer · Leads backend engineering

    Responsible for

    Designs and owns backend architecture, integrations and background-job systems for SaaS products.

    Experience

    • Owned core subsystems of a multi-tenant care-coordination platform used by hospital systems: the EHR integration layer, patient-journey automation and tenant-scoped job infrastructure.
    • Backend work on Sokkat, a UAE e-commerce app, and full-stack work on a multi-country online tutoring platform.

Values

  • Say no early

    When a project is not a fit, we tell you in the first conversation instead of taking it on.

  • Claim only what we can show

    We list only the work we have evidence for, and link each claim to a case study or a profile.

  • Write decisions down

    We keep a decision log and show working software every week, so you always know what changed and why.

  • Put the rules in one place

    Tenancy, consent and money logic are enforced in one place and proven with tests, not re-checked in every feature.

Want to know who would work on your project? Tell us about it.

Discuss your projectSee our work