Web applications and internal tools
The system your operation actually runs on, replacing the spreadsheet three people keep their own copy of. The process stops depending on who remembers the exceptions.
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.
The system your operation actually runs on, replacing the spreadsheet three people keep their own copy of. The process stops depending on who remembers the exceptions.
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.
Two systems that do not talk, so somebody re-keys between them. Or an application that still works and nobody dares touch. Both are fixable without betting the business on a rewrite.
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.
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.