Five shapes most projects turn out to be.
Most of what comes through the door fits one of the first four. The fifth is what happens when the same discipline gets pointed at something bigger.
Consumer and lifestyle apps
iPhone, iPad and web from one codebase, with accounts, sync and subscriptions — the kind of app a customer opens every day, not once and forgets. Built to be maintained long after launch, not just shipped and left.
Portals for small companies
The internal thing staff or customers sign into — bookings, records, requests, approvals — built around how the work actually happens rather than how an org chart says it should.
Replacing the spreadsheet
The one file the business actually runs on, turned into something that cannot be emailed to the wrong person, overwritten by two people at once, or lost when the one person who understands the formulas leaves.
Automating the manual step
The re-keying, the copy-paste between two systems, the Monday report built by hand every week — found and removed, not just documented as a known problem.
Internal tools & enterprise-scale systems
The same portfolio-management discipline that ran technology programs spanning hundreds of applications applies just as well to a single system built to last: role-based access from day one, data handling that accounts for real privacy and compliance requirements, and architecture that does not have to be rebuilt if it grows past its first thousand users. Not every project needs this level of rigor — but when one does, it is already how we work, not a different mode we switch into.
Not sure which of these fits what you have in mind? That is exactly what the first conversation is for.