Case Studies
Client names are left out on purpose, and a couple of details are blurred so nobody is identifiable. The numbers are real.
Where we usually get called in
Four situations account for most of our first calls. If one of them sounds like your week, we have done it before.
The person who knew everything left
Nobody has the passwords, the server was set up by somebody who moved to Georgia, and there is no documentation. We start with an inventory and work outward.
Two systems that will not talk
Usually an accounting package and something operational, joined today by a person retyping numbers. Most of these are a two week integration, not a new platform.
The closet server is failing
It is out of warranty, the backup has not been tested, and everyone knows it. This is the most common reason a migration conversation starts.
Growth broke the spreadsheet
The workbook that ran the business at twelve people falls over at forty. Usually the fix is a small internal tool, not an ERP.
A migration, start to finish
A logistics broker in Doral, twenty six staff, running everything off two aging servers in a storage room with a window air conditioner pointed at them. Six weeks from first call to cutover. Here is how it went.
Week one, inventory
We found eleven services running. Four of them nobody could explain, and two turned out to be unused since 2021.
Week two, the plan
Written, costed, and short. Nine pages including the rollback procedure and the list of things we deliberately were not moving.
Weeks three and four, build
New environment on AWS, running alongside the old one. Nothing switched over yet, which is the point.
Week five, dry run
A full rehearsal on a Saturday morning with the old system still live. Two problems surfaced. Better then than during the real thing.
Week six, cutover
Friday evening to Sunday afternoon. Staff came back Monday to the same shortcuts and the same file paths, which was the brief.
Afterwards
Monthly bill landed at 480 dollars against 1,100 in hardware amortisation and power. Payback came in under a year, which is faster than usual.
The Complete Website Toolkit for New Possibilities
A clinic that needed a tool, not a platform
Three locations, one referral process, tracked in a shared spreadsheet that two people edited at the same time and regularly clobbered. Vendors quoted a practice management system at 40,000 dollars and eight months. We built a small referral tracker in five weeks for a fixed 14,000, connected it to what they already used for scheduling, and left them the repository. It does one job. That was the requirement.
Taking over from a provider who had stopped answering
An accounting practice, nineteen people, two months into a support contract where tickets went unanswered for days. We ran alongside the incumbent for three weeks rather than cutting over, which is how we found the backup job that had been failing silently since March. Their previous provider had never checked a restore. Nobody had.
Inventory on a website, without an API to work with
A boat dealership on the river wanted its inventory on the website and updating itself. The dealership software had no API, so we read its nightly export instead, which is unglamorous and has run without intervention for two years. Fixed price, 9,200 dollars, delivered in seven weeks. Sometimes the boring answer is the durable one.
The best way to work together. Safe, secure and reliable.
- Make your customer service stand out.
- Customize your reports and get insights into the metrics that matter.
- Improve communication and makemassive amounts of data.