Your design studio delivered the job on time and nobody can say whether it made money

Job costing with time and margin tracking runs NZ$30,000 to NZ$55,000 across 8 to 12 weeks. Adding variations, materials and capacity planning takes it to NZ$55,000 to NZ$85,000. Under about eight people, Asana or Monday plus a time tracking tool covers most of it.

Because they model tasks, not contracts. Neither carries a quoted value, budgeted hours by role, or a margin that updates as work is logged, so a job can show green while losing money. Their add-ons for budgets are shallow and break the moment variations enter the picture.

Through a variation record created in seconds with a description, a price and a request for client approval by email, logged against the job. The discipline is cultural rather than technical, but making it a ten second action rather than a form removes the excuse that stops it happening.

Only if it takes seconds. Design the entry experience first and everything else second, with sensible defaults, recent jobs surfaced, and entry available on a phone. Studios that impose a clumsy timesheet get compliant fiction, which is worse than no data because people believe it.

Yes, with materials committed at order rather than at delivery so work in progress is truthful, and subcontractor costs attached to the job when the purchase order is raised. For a fabricator, materials commitment visibility is usually worth more than the labour tracking.

It should, generating invoices from job milestones or approved variations rather than requiring re-entry. Keep Xero as the ledger and let the job system own the operational detail, which keeps your accountant on familiar ground and avoids a general ledger rebuild nobody needs.

Yes, through a client view with explicit permissions showing milestones, approvals and deliverables while hiding costs, rates and margin entirely. Get the permission model demonstrated rather than described, since accidental exposure of your rates to a client is not a recoverable mistake.

Eight to eighteen weeks to build, then one full job cycle before the numbers can be trusted. For a studio running three month commissions, expect meaningful margin insight at around six months. The first accurate quarter is usually uncomfortable and extremely valuable.

Yes, including the costing rules, which encode decisions about how you value time and allocate overhead. Contract the repository under your organisation and require documentation of the margin calculation, because that logic is the part a future developer must understand before changing anything.

Start with the three that move money and attention: Slack or Teams for notifications, calendar sync for deadlines, and your accounting tool such as QuickBooks or Xero so tracked time flows into invoices without retyping. Development teams usually add GitHub or GitLab so tasks close when code merges. Each solid two-way integration adds roughly 1 to 2 weeks of build time, so rank them by hours saved per week rather than wishlist order.

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.

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.

The non-negotiables are single sign-on, role-based permissions, encryption in transit and at rest, and an audit log of who changed what. If client work under NDA lives in the tool, custom actually improves your position, because you can run single-tenant on your own cloud account instead of shared SaaS infrastructure. You only need SOC 2 certification if you plan to sell the tool to others; for internal use, an annual penetration test is the sensible spend.

Yes: a custom layer on top of a tool you already pay for. Digital Heroes ships client dashboards, automated reporting, and workflow glue built on the Asana and ClickUp APIs for $8,000 to $20,000, which fixes the specific gap without replacing the whole tool. A full custom platform rarely makes sense below roughly 50 seats unless the software faces your own customers.

Plan on one product owner from your side spending 3 to 5 hours a week reviewing sprint demos, answering workflow questions, and testing before releases. Digital Heroes builds run discovery for 2 to 3 weeks, then two-week sprints with a clickable demo at the end of each. If your team is in Whanganui, a one or two day on-site discovery workshop at the start is worth doing; everything after that works identically over calls.

Digital Heroes builds custom project management 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 Whanganui. You can chat with the team directly, and every form gets an email reply within 24 hours.