What we do
- Technology Stack Assessment ‒ Evaluation of existing technology stack and processes to identify problems and opportunities.
- Systems Integration ‒ Bespoke integrations and customisation between existing systems and platforms.
- Technical Documentation ‒ User and technical documentation written in context of the client's domain and technology stack.
- Vendor Selection Advisory ‒ Independent vendor evaluation against real business requirements. Covers requirements discovery, comparative assessment, sales process support, and technical due diligence including platform lock-in analysis.
- █████████████ ‒ ███████████████████████████████████████████████████████████████
- Technology Deployment ‒ Implementation and configuration of selected technology solutions, including data migration, workflow setup, and handover documentation.
Case studies
A consignment retail store was spending several hours each week on vendor billing. The process was entirely manual: exporting sales data, sorting by vendor in a spreadsheet, then creating invoices in their accounting platform one by one.
We built an automation that ran locally from their desktop, pulling sales data directly from their retail platform and grouping it by vendor automatically. It generated a self-balancing verification spreadsheet with links to draft invoices. Items sold as unknown at the point of sale (typically SKUs the cashier couldn’t identify) were flagged for manual reconciliation. We also redesigned the invoice template so vendors received something that looked like a payout statement: familiar and readable rather than a generic accounting document. The solution was designed around how they'd actually use it, not just how it worked.
The weekly billing run went from several hours to around fifteen minutes.
An accounting practice was running their work-in-progress across two disconnected platforms. Jobs were falling through the gaps and there was no single view of where work stood at any given time. They wanted an integrated practice management solution.
Rather than accepting vendor presentations at face value, we sat in on demos for two platforms, asking technical questions the sales process wouldn't surface and debriefing with the client afterwards to separate genuine capability from sales pitch. One platform had appealing features but would have required the practice to reshape how they worked to fit the software. The other was the better fit.
We managed the full implementation: migrating client data from the existing platform and recreating active jobs to match current work in progress. To cover the transition period, we designed an interim manual process to ensure nothing was missed while both platforms were live. We also ran informal training on the features central to solving the visibility problem.
A feature on the requirements list turned out not to be supported. We caught it during implementation, managed expectations, and the client determined they could work around it without impacting the outcome.
The practice now runs all work through the new platform with full visibility.
A professional services firm was managing client bookings through a personal calendar. New bookings required manual checks to ensure onboarding preparation was completed and the right people were informed before a client arrived. There was no visibility across the team without exposing the calendar directly.
We built an integration using existing infrastructure that triggered automatically on new bookings, creating a note in their practice management platform linked to the relevant contact and work. If either didn't exist yet, the note flagged it explicitly rather than silently assuming. The right people had visibility of incoming clients in the context of the work being done for them, without needing access to anyone's personal calendar.
A daily summary email was also built into the integration, consolidating upcoming bookings with the relevant client and work context in one place.
The manual check process was eliminated. Onboarding and preparation now happen as part of the same workflow, not as a separate manual step, and the whole team works from the same picture.
Meet the team
A former software engineer with seven years in retail technology, someone who makes complicated things make sense. Jack started SaaSquatch to give small businesses access to the advocacy and support typically reserved for larger enterprises. He listens carefully enough to surface the real problem, and builds solutions that fit the way people already work.
Malcolm operates at a frequency of uncomplicated joy. He has a genuine interest in what people have to say, and the rare quality of making them feel it. He fits in anywhere and lifts the room without trying. The stick was never the point, but he will still chase it.