Your Swansea books balance in Xero and still can't survive a Welsh Government grant audit without a spreadsheet

They can record the transactions, but Xero has no native concept of a fund, an eligible category, a claim period, or clawback risk, so the grant view gets rebuilt by hand each audit. A custom layer over Xero encodes those rules so the reconciliation and audit export are automatic. Your accountant still runs the commercial books; the layer handles the fund accounting Xero can't.

Build on top, almost always. Xero and QuickBooks do VAT, Making Tax Digital, and the GL well and cheaply, and rebuilding that is wasted money. The right shape is a grant-and-fund layer that reads from your existing ledger and adds the eligibility, reconciliation, and reporting intelligence. A developer pushing a full ledger replacement for grant reasons is usually overselling.

It matches what you submitted to a funder against what you actually spent in the ledger, flagging mismatches before an auditor finds them. Today that's a manual spreadsheet exercise prone to error, and errors mean disallowed costs and clawback. Automating it protects the funding and saves the recurring finance time, which is often the clearest single payback on the build.

If you hold public-sector contracts or report to Welsh Government bodies, bilingual statements can be expected or required, and building them in avoids manual translation. For a purely commercial business with no public-sector exposure it's optional and gets scoped out. As with the rest of the build, it's decided in discovery so you only pay where it genuinely applies.

When grants are a small, simple part of your finances with few costs and infrequent claims, a well-kept spreadsheet beside Xero is cheaper than a build and entirely defensible. The case for custom kicks in when grant funding is material, audits are recurring, and the manual reconstruction is costing real finance time and risking clawback. An honest developer will tell you which side of that line you're on.

Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.

If you own the repository, the hosting accounts, and the documentation, another team can take over within weeks, usually before a missed closing cycle does real damage; if the agency owns any of those, you have a hostage situation. Before signing, confirm the code sits in your GitHub or GitLab organization, hosting bills to your card, and a written deployment runbook exists. A competent agency agrees to all three without friction, and hesitation is itself the answer.

The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.

Location matters for discovery, not for code. If your workflows involve a warehouse, job sites, or a back office in Swansea that a developer should walk through, a few on-site scoping days are worth paying for; after that, remote delivery works fine and widens your options. Judge candidates on shipped accounting systems and communication cadence, not office proximity.

A focused first version takes 10 to 16 weeks, and a complete QuickBooks-class replacement takes 6 to 9 months. In Digital Heroes delivery data, schedules slip most often during data migration and bank feed integration, so we budget those two phases at double the first estimate. Treat any promise of a full accounting system in under two months as a warning sign.

Ask to see a live accounting or fintech system they built, then ask how they handle double-entry integrity, period closing, and audit trails; a team that has never built a ledger will learn on your budget. Check whether they bring an accountant or finance-literate analyst into scoping sessions. A portfolio proves design skill, but a walkthrough of how their system blocks an unbalanced journal entry proves domain skill.

A boring, proven one. Digital Heroes defaults to PostgreSQL for the ledger because transactional integrity is non-negotiable, a typed backend such as Node with TypeScript, .NET, or Java, and standard React on the front end. The avoid list is clearer than the pick list: floating point math for money, a NoSQL database as the primary ledger store, and any framework young enough that hiring for it in three years will be a problem.

At minimum: encryption at rest and in transit, role-based access control, and immutable audit logs recording every change to the ledger. If outside parties rely on your numbers you will want SOC 2 style controls, and storing card data pulls you into PCI DSS, which most builds avoid by tokenizing payments through Stripe or a similar processor. Your industry adds its own rules, so compliance requirements belong in the written spec, not in a post-launch retrofit.

In the competing quotes clients share with Digital Heroes, established US and UK agencies charge $90 to $200 an hour for accounting and fintech work, senior freelancers $60 to $150, and offshore teams $25 to $60. We price accounting builds as fixed-scope milestones instead, because hourly billing on ledger work rewards slow debugging. Compare total quoted cost against your workflow list rather than comparing rates against rates.

Move when you are paying people to work around the tool, not when the subscription feels expensive. Common triggers are hitting the 25-user cap on QuickBooks Online Advanced, consolidating multiple entities in spreadsheets, or a billing model that forces manual journal entries every month. If your team spends several hours a week exporting to Excel just to answer basic questions, you are already paying for custom software in salaries.

Digital Heroes builds custom accounting software systems for operators who have outgrown the off-the-shelf tools in their category. The work is delivered remotely: our engineers work from Delhi and Lucknow, leadership is in New York, and some team members live in London and Sydney and work remotely from there. We have no office in Swansea. You can chat with the team directly, and every form gets an email reply within 24 hours.