Industries

We work best where a mistake is expensive

Healthcare is where we started, and it taught us to test carefully, write things down and stay through go-live. Those habits apply anywhere a mistake is costly. Below are the questions organizations in each sector tend to ask, and how we would answer them.

Hospitals & Health Systems

Epic build, testing and go-live support, from someone who spent thirteen years inside Ontario hospitals.

A typical call

We're three weeks from go-live, testing isn't finished, and the analyst who built half of it just gave notice. Can you help?

What we'd do

Yes. We'd start by sorting the open issues into what blocks go-live and what can wait. Then we'd pick up the unfinished build ourselves so the gap doesn't land on the rest of your team, and stay through go-live and the weeks after it.

Our sites merged, but their order sets never did. Where would you start?

With the clinicians who own them. We'd put the two versions side by side, agree with each specialty which one becomes the standard, then build, test and retire the old ones in stages so nobody loses an order they rely on.

We have an analyst vacancy that will take months to fill. Can you cover it?

Often, yes. We can take the seat ourselves or bring in an experienced Epic analyst we know, for as long as it takes you to hire.

Usually: a delivery engagement through go-live and stabilization, or an analyst placement.

Long-Term Care & Community Health

Practical IT help for small teams carrying hospital-level obligations.

A typical call

An auditor asked when our backups were last tested, and nobody knows. What now?

What we'd do

We'd restore a backup with your IT person that week, time it, and write down how it went. Then we'd look at the rest of the setup and agree on the two or three things worth fixing first.

We have one IT person. Can you help without overwhelming them?

Yes. We start with a short review and only recommend what your team can keep running after we leave. If they need cover for holidays or busy periods, we can provide it, with response times agreed up front.

We need a new system, but nobody has time to choose one properly. Can you run the selection?

Yes. We'd write down what you actually need, shortlist the vendors, run the demos with your staff and check references, so you can make the decision with good information.

Usually: a short review that becomes ongoing support.

Public Sector & Not-for-Profit

Delivery planned around procurement rules, audits and budget years.

A typical call

We have to buy through a formal procurement. Can you help us write requirements vendors can respond to?

What we'd do

Yes. We'd work with your staff to describe what the system needs to do in plain terms, turn that into requirements and scoring criteria that fit your procurement rules, and help you evaluate the responses.

The last project here didn't land, and staff are tired of change. How would you approach the next one?

By asking the people who will use it what went wrong last time, and planning around their answers. We keep each phase small enough to show results early, and we train people using their own day-to-day tasks.

Our budget is set by fiscal year. Can the work fit that?

Yes. We plan the work in phases that line up with your budget year, and we'll tell you if a phase should wait for next year's budget.

Usually: advice and delivery, phased to your budget cycle.

Professional Services & Mid-Market Enterprise

For growing firms whose systems and processes haven't kept up with the business.

A typical call

We've grown fast and our processes are held together by spreadsheets. Where do we start?

What we'd do

By watching how the work actually happens. We'd map the process as it runs today, find where time and errors pile up, and give you a short list of changes in order of payoff, whether or not new software is part of it.

We've been trying to choose a new system for a year and can't agree. Can you help?

Usually the hold-up is that nobody agreed on what the system must do. We'd settle that with the right people first, shortlist vendors against it, and help you decide. If you want, we'll then set it up and stay through the switchover.

Our IT support is one overworked person and a lot of goodwill. What would you change?

We'd check backups, security and how requests get handled, fix what's risky first, then set up support with clear response times, working alongside your person or covering for them.

Usually: a short discovery that turns into delivery. The discovery report is yours to keep, whoever does the work.

Work in a different sector?

Get in touch anyway. Planning a system change, testing it and helping people through the switch works much the same way in most organizations. If your project isn't a good fit for us, we'll say so early.

Talk to us