Xero tells you the Derby shop made money last month, but not which jobs lost it

Xero and QuickBooks are general ledgers that think in invoices and expenses, not jobs, parts and machine hours. They can report overall profit but cannot tell you which job carried the margin and which lost money, because per-job cost capture and WIP valuation are simply outside what a general ledger does.

No, and most Derby firms should not. The custom job-costing layer sits on top of Xero or QuickBooks, which keeps doing the statutory ledger, while the layer owns per-job costing, WIP and margin reporting. Integration keeps both in sync.

By reconciling actual job cost against the estimate and feeding the result back to estimating. Over time you stop winning underpriced jobs and losing padded ones, because the next quote is grounded in what similar jobs actually cost rather than gut feel.

Yes. It tracks the cost accumulated on a job between quote and invoice and reports it as WIP, so the asset sitting on your shop floor finally appears on the balance sheet instead of being invisible until the job is invoiced.

Budget $12k to $28k a year for support and enhancements. The real ongoing requirement is disciplined capture of machine and labour time per job, because the costing is only as accurate as the time data your shop floor records.

Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.

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.

Typical payback in Digital Heroes accounting projects is 18 to 36 months, driven by recovered labor hours and fewer billing errors rather than saved subscriptions. A business spending 30 hours a week on manual reconciliation and rebilling can justify a $75,000 build inside two years at ordinary bookkeeper rates. If your projected payback stretches past five years, extend your current tools instead.

It encodes your actual business rules: progress billing tied to project milestones, revenue recognition for your specific contract types, landed cost tracking, or approval chains that match your org chart. Off-the-shelf tools handle generic bookkeeping well but force every business into the same chart of accounts and workflow. FreshBooks, for example, is built around freelancer-style invoicing, so inventory or multi-entity accounting means leaving the product entirely.

A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.

The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.

It scales exactly as far as its data model was designed to, so multi-entity support, multi-currency, and consolidation should be day-one design decisions even if you launch with a single company. Retrofitting multi-entity onto a single-entity ledger is among the most expensive changes we handle, and in Digital Heroes rescue work it often costs a third of the original build. Compare that with QuickBooks Online, which requires a separate subscription for every company you add.

Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.

Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.

Yes, but scope it around one complete workflow rather than a thin slice of everything. A strong first release fully owns, say, invoicing and receivables while QuickBooks keeps running the general ledger, letting you validate the software with real money movement in 10 to 14 weeks. In Digital Heroes projects, one-workflow MVPs reach a stable full system faster than big-bang replacements almost every time.

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.

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.

Yes, and it should be treated as standard scope rather than an add-on. Bank feeds typically come through aggregators like Plaid, payments through Stripe or your existing processor's API, and payroll providers such as Gusto and ADP publish APIs for pulling journal entries. The real constraint is smaller regional banks without feed coverage, which is worth verifying during scoping instead of discovering after launch.

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.

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 Derby. You can chat with the team directly, and every form gets an email reply within 24 hours.