Web applications and internal tools
Replaces the spreadsheet three people keep their own copy of, and the process that only works because one person remembers the exceptions. What the team does every day, encoded properly.
Six kinds of work, listed in the order they usually matter. The surface changes; the method does not — understand the problem before proposing a solution, build something that can be maintained, and hand it over so you own it outright.
Replaces the spreadsheet three people keep their own copy of, and the process that only works because one person remembers the exceptions. What the team does every day, encoded properly.
The same engineering, done by someone who already knows that a file which parses cleanly can still be wrong. You stop paying a vendor to learn the domain on your time.
Applied to work people currently do by hand: reading documents, sorting queues, drafting replies. Built into the software you already run, with a person approving anything that matters.
iOS and Android for staff in the field and for customers. Offline behaviour, store review and release management are part of the work rather than surprises after launch.
Marketing sites, content sites and landing pages built for speed, accessibility and search. A site with one job it does well, that your own team can edit.
Google Maps and local search for US home-service companies. We manage the profile that decides who gets the "near me" call, and the pages on your site that back it up.
Four stages, in this order, each with something you can hold at the end of it.
Claims and billing workflows, data exchange between systems, reconciliation, audit trails, role-based access, and AI applied to the document work that consumes a billing team's day. It is the area we know best.
Describe the problem rather than the solution. Working out which shape it is comes first, and that conversation is free.