Contact
Come with the problem, not a specification.
You do not need a brief, a budget or a technical document. Describe how the work gets done today and where it hurts — that is enough for a first conversation.
Send a requirement
A few lines is fine. I reply within one business day.
What happens next
- A reply within one business day — with a couple of questions if the requirement needs clarifying.
- A free 30-minute call — where the closest module is walked through against your actual process, not a demo script.
- A written scope and quote — or an honest note saying software is not the right fix here.
Questions
Before you write.
I do not know what I need yet. Is it still worth calling?
Yes — that is the normal starting point. Describing how the work happens today is enough. Working out what should be built is part of the first conversation, not a prerequisite for it.
Do you work with businesses outside healthcare?
Yes. The hospital work is simply where most of the history is. HRMS, inventory, purchase approvals, recruitment and asset management are sector-neutral and suit any multi-branch operation.
Do you take on small projects?
Yes. Spreadsheet automation and single-module deployments are deliberately small, fast engagements — often the sensible first step before committing to anything larger.
Can you work with our existing developer or IT team?
Yes. Handing over documented source code is standard practice here, so working alongside an in-house team, or building something they will maintain afterwards, is straightforward.