One Year of Building Swifty
A year ago, Swifty was an idea backed by a small codebase and a set of convictions about how business software should work. Today, it's a platform running real workspaces for real teams, with a feature set we couldn't have fully anticipated at the start.
Looking back at the year, a few things stand out.
What We Got Right Early
Starting with the definition system was the right call. Building a flexible, configuration-driven platform requires a solid foundation for expressing what things are and how they behave. The investment in getting that right early paid dividends as every feature added on top of it.
The decision to go generic from the start — rather than building for one industry or one use case — was harder to justify a year ago than it is today. But it's what allowed Swifty to serve meaningfully different business types with the same underlying platform.
What Surprised Us
The degree to which small UX improvements compound. Inline editing, smart badges, instant search — each of these felt incremental when we shipped them. The cumulative effect of many incremental improvements turns out to be a platform that feels noticeably different to use than it did six months ago.
Performance mattered more than we expected, earlier than we expected. As soon as workspaces moved to real operational data, the difference between fast and slow became concrete and urgent. We've done multiple rounds of performance work, and each one produced tangible improvements for users.
Where We Are Now
The platform today can handle the full operations of a small-to-medium business: contacts, projects, invoices, contracts, workflows, notifications, documents, integrations. Not as a collection of separate modules but as a unified system where all of these are connected.
That's the vision we articulated a year ago, in rough form. It's more realized now than we expected it to be.
What's Next
Year two is about depth and scale. Taking the capabilities we've built and making them more capable — more flexible workflow logic, richer document generation, more powerful search, better tooling for complex multi-department operations.
And performance. There's always more performance work to do.
The first year was about proving the approach. Year two is about making it exceptional.