Most business software is designed for a company that doesn't exist. It assumes a dedicated IT team, a training budget, staff with slack in their day, and processes that bend to fit the product. Then it meets a real Welsh SME: eight people, everyone wearing two hats, and a process shaped by twenty years of actual customers.
We build for the real version. And after years of doing it from Swansea, we've learned that software for an SME isn't a scaled-down version of enterprise software. It's a different discipline, with its own rules.
In a small firm, the "sales system user" is also the delivery scheduler and, on Thursdays, the credit controller. Design for the roles people actually hold, in combination, rather than an imaginary average user, and the system fits like it was made here. Because it was. This is why the process starts with watching the work, and why a good brief describes your Tuesday, not your ambitions.
An SME's first release should be modest, useful and quick to trust: the core records, the core workflow, the exceptions handled honestly. Growth gets a route, not a bill. Build the foundations so that customer accounts, another site or an online shop can be added, without paying for any of them before they're needed. Overengineering is just as expensive as underengineering; it simply sends the invoice earlier.
Your accounts package works. Your specialist industry tool works. Ripping out working software to satisfy a grand unified vision is an enterprise habit, and SMEs can't afford enterprise habits. Connect the specialist tools, replace only what's genuinely failing, and spend the bespoke budget where your business is actually distinctive.
Serving your customers might mean Welsh language options, and serving your operation definitely means support from people in your time zone who know your system personally rather than a ticket queue reading from a script. Continuity matters too: documentation and knowledge that survive any one person, on your side or ours, so the business is never one departure away from a mystery.
The test of an SME system isn't what it can do in a demo. It's whether Tuesday got better: fewer retypes, faster answers, exceptions that surface instead of hiding, and a team that trusts the screen in front of them. That's the standard behind our bespoke software and web application work, from client portals like Darkin Architects' to the systems quietly running operations across South Wales, all with local support behind them.
Trust, in the end, is built the unglamorous way: collaboratively, release by release, by people who'll still answer the phone in year three. If you'd like software shaped around your firm instead of the other way round, you know where we are. Just up the road, mostly.