Specialist-led software agency
Software built by the people who will answer for it.
We build backend systems, integrations, and SaaS products—with a named engineer responsible from architecture to production.
- ClientsNext.js · React · Flutter
- AuthAuth0 · tenant + role
- APINode.js · FastAPI · Rails
- JobsBull · Celery
- IntegrationsFHIR · Stripe
- AILLM · voice
- DataPostgreSQL · MongoDB
// The tenant travels with every job.await queue.add("journey.step", { tenantId: ctx.tenantId, patientId,}, { jobId: `${ctx.tenantId}:${step.id}` });Proven in production
Multi-tenant healthcare systems
A care-coordination platform used by hospital systems, connected to several EHR vendors over FHIR and HL7, with every query, job and cache key scoped to the right hospital.
AI voice agents
An AI voice agent that answers dealership calls and books appointments, on two voice providers behind one switch.
Sites AI assistants can cite
A 270-page bilingual site audited for AI search, with validated JSON-LD on its priority pages and corrected hreflang.
Practices
Practices, each led by someone who has shipped it.
We take on the work our leads have done before. If your project needs something else, we will say so.
Backend and platform engineering
APIs, multi-tenant SaaS backends, integrations and background-job systems that hold up in production.
Muhammad Tahir Hassan KhanPractice leadHubSpot and CRM automation
Workflow automation, custom HubSpot development and the integrations that keep HubSpot in sync with NetSuite and the rest of the business.
Muhammad HuzaifaPractice leadAI voice agents and full-stack SaaS
Full-stack SaaS products built end to end, with production AI features: real-time voice agents, LLM tool calling, transcript pipelines and vector search.
Burraq Ur RehmanPractice leadHubSpot CMS, migrations and AEO
HubSpot CMS sites, portal migrations and merges, and sites made readable for search engines and AI assistants.
Muhammad UsmanPractice leadShopify and WordPress development
Shopify stores, WordPress and WooCommerce sites, and PHP and Laravel work for businesses that sell online.
UsamaPractice lead
Selected work
Problems solved in production.
Work by our practice leads, shown with context. Client names are withheld where agreements require it.
Problem
Coordinating each surgical patient's journey was largely manual, and every hospital ran a different EHR.
What changed
An automation engine for the patient journey, one FHIR-based integration layer for every EHR vendor, and tenant scoping enforced at the data layer.
Result
Patient coordination became automated across hospitals, and a class of timezone and data-mismatch errors that contacted patients at the wrong time was eliminated.
Delivered by Tahir as a backend engineer at a healthcare technology company, before Carpediemsoft.
- Node.js
- Express
- MongoDB / Mongoose
- Redis
Problem
Dealerships were losing revenue to missed inbound calls and dropped follow-ups.
What changed
An AI voice agent that answers inbound calls and books appointments through real-time tool calling, on two voice providers behind one switchable abstraction.
Result
Calls are handled automatically, and the platform can move between voice providers with zero downtime.
Delivered by Burraq as the engineer on Otto Revenue Engine, before Carpediemsoft.
- Python
- FastAPI
- async SQLAlchemy
- PostgreSQL
Problem
A boutique real estate agency needed a bilingual site whose listings were managed in the CRM, not maintained as static pages.
What changed
Listings became a HubSpot custom object rendered by one template pair in both languages, with SEO faults fixed at the template level.
72%fewer flagged SEO issues
Result
The site-wide SEO scan fell from 3,266 flagged items to roughly 900, and 150+ property pages now come from CRM records.
Delivered by Usman as the developer for a boutique real estate agency.
- HubL
- CRM custom objects
- Memberships
- Cloudflare Workers
How we work
A written process, from first call to running software.
Every stage ends in something you can read, check or run.
01
First conversation
Thirty minutes with the practice lead to understand the problem, the system it lives in and who depends on it.
You get: A clear answer on whether we are a fit.
02
Scoping
The lead who will build the work writes down what will be built, how, and what could go wrong.
You get: A written scope with approach, risks and price.
03
Build in the open
Weekly demos, written decisions and a shared board, so you always know what changed and why.
You get: Working software every week, with a decision log.
04
Ship and prove
Tests run on the real database engine, the rollout is staged, and the handover is written down.
You get: A staged release and a documented handover.
05
Run and improve
Optional retained support once the system is live, with agreed response times.
You get: A support agreement, if you want one.
Who you'll work with
A named lead on every practice.
Muhammad Tahir Hassan KhanBackend engineering lead
Muhammad HuzaifaHubSpot and CRM automation lead
Burraq Ur RehmanAI voice agents and full-stack SaaS lead
Muhammad UsmanHubSpot CMS, migrations and AEO lead
UsamaShopify and WordPress development lead
Why Carpediemsoft
The same standards on every project.
The rules our leads already work by, written down so you can hold us to them.
Critical rules are structural
Tenancy, consent and money logic are enforced in one place, not re-checked in every feature.
Root cause, not symptom
A bug is fixed in the shared path every caller goes through.
Humans stay in the loop
Where safety is involved, a person reviews what the system produces.
Questions
The things people ask before they write to us.
How big is Carpediemsoft, and who actually does the work?
We are a small company: one owner and a named lead for each practice. The lead who scopes your project is the one who builds it. Work is never handed to people you have not met.
Can you work inside our existing codebase?
Yes. Audits, root-cause fixes, tests that prove the concurrency and money logic, and safe expand/contract migrations are part of the backend practice. We start by understanding what is there before changing it.
How do you price and structure engagements?
Every engagement starts with scoping, and scoping ends in a written document with the approach, the risks, the timeline and the price. Nothing is billed before you have agreed to that document.
Can we sign an NDA before we talk?
Yes. Send it with your message and we will sign it before the first call.
What happens after we send a message?
We read it and reply by email. Then a 30-minute call with the practice lead to understand the problem, and after that a written proposal with scope, approach, timeline and price, or a clear no if we are not the right fit.
What kind of work is not a fit?
We take on the work our leads have done in production. At the moment that is backend and platform engineering, HubSpot and CRM automation, AI voice agents and full-stack SaaS, HubSpot CMS, migrations and AEO, and Shopify and WordPress development. If your project needs something else, we will say so in the first conversation.
Contact
Tell us what you're building.
A few plain sentences about the system and the problem are enough to start.
What happens next
- We read your message and reply by email.
- A 30-minute call with the practice lead to understand the problem.
- A written proposal with scope, approach, timeline and price, or a clear no if we are not the right fit.