Straight answers to the questions we get most often.

Advisers first. Every engagement starts with an assessment and a costed plan, and you own that plan outright: you can execute it in house, hand it to another partner, or ask us to deliver it. We are able to implement, and often do, but the advice comes first and stands on its own.

We hold no reseller agreements, take no referral fees and have no product of our own to protect, so there is nothing riding on which platform you choose. Advisory is priced and scoped as its own piece of work, so it pays for itself whether or not delivery follows. And because we would be the ones building it, we have every reason not to recommend work that will not succeed.

Yes, and plenty of clients do. A fixed-price assessment gives you the diagnosis, the priorities, the platform recommendation and realistic costs and timescales, in a form your board or your own IT team can act on. No obligation to use us for delivery.

Property businesses of every kind. Developers, asset managers, managing agents and landlords, construction and fit-out businesses, facilities and estate operators. We are not a single-trade specialist: buildings, leases, assets, works and the money attached to them are one connected data problem, and we work across all of it. If your data is holding the business back, we are a fit.

All three, always starting from advisory. Most work begins with an assessment, then becomes either a defined delivery project (migration, implementation, integration) or a retained engagement where we advise on and run part of your data and technology function. For scale-ups we often embed a senior operator into the leadership team.

Advisory assessments are fixed price and scoped to your situation, not to a set number of weeks. Delivery work is scoped after the assessment and priced against outcomes. Retained and embedded engagements are monthly. We share indicative ranges on the advisory call so you never lose time on a proposal that will not fit the budget.

We are vendor neutral. In practice we spend most of our time in and around the stacks these businesses run on: field service and job management tools such as ServiceTitan, Simpro, BigChange, Joblogic, Commusoft and Salesforce Field Service, CAFM and EAM platforms such as Planon, Concept and Maximo, property systems such as Yardi and MRI, and the accounting, payroll and BI tools around them: Xero, QuickBooks, Sage, NetSuite, SAP, Dynamics, Power BI.

Both. Where an off-the-shelf platform fits, we help you choose, configure and adopt it. Where nothing on the market fits, we build the software you need, designed around your operations and integrated into your existing stack.

We work under NDA by default and treat your data as confidential. We can work inside your environment, use our own tooling, or a hybrid, whichever fits your security posture. See our security page for more.

Advisory assessments normally start within two to three weeks of the advisory call. Larger delivery work depends on scope; we will tell you what is realistic, not what sounds impressive.

We work remotely with clients internationally, and on site where the engagement needs it. Most delivery happens through your systems, not in a room, so location is rarely the constraint. Time zone overlap and language are what we check up front. We will always be straight about where we are and are not the right partner.

Yes. This is one of the most common first projects. We pull certificates, test results, commissioning sheets, safety and inspection records, RAMS and sign-offs out of email, shared drives and paper, attach them to the right job, asset and site in your system of record, and make sure the mobile app captures them correctly from that point on. The outcome is a record you can produce in minutes instead of reconstructing it.

We model the contract properly: assets, visit frequency, entitlements, exclusions and renewal dates. Then we generate the planned visits from that model instead of from memory or a spreadsheet, so missed visits and unbilled contract work become visible before the client notices, and renewals come with a real service history behind them.

Yes. We build a completeness view that checks each completed job against what it should have (job sheet, photos, certificate, signature, asset reading) and flags gaps by team, contract and site. Most clients use it as a weekly exception list, so audit week stops being a scramble.

We consolidate asset registers so each piece of plant has one identity, one location history and one work history, including serials, warranty dates, meter or hours readings and previous faults. That is what makes reactive calls faster and end-of-life or replacement conversations credible.

We track competencies and expiry dates against each person, then surface them where scheduling actually happens, so work is not assigned to someone whose ticket lapsed last month. Reminders run before the expiry date, not after it.

That is the core of most engagements. We map the real path from enquiry to estimate, approval, job, schedule, site visit, completion, sign-off, invoice and payment, then remove the re-keying, duplicate records and manual handoffs between them. Typically this is a mix of configuring the job management platform properly and integrating it with finance.

It depends where you start, but the pattern is consistent: when job completion data is captured on site and flows straight into billing, weeks come out of the cycle. In representative engagements we have taken job-to-invoice from around three to four weeks down to a few days. The bigger win is usually cash predictability, not the headline number.

Yes. We build a costed rate and price library (labour rates, uplifts, standard assemblies, materials) so quotes are built from the same basis every time, and margin is visible at quote stage instead of discovered at month end. Estimators keep judgement; they stop rebuilding arithmetic.

We put variations into the same flow as the original job: raised on site, priced from the same library, approved with a record, and carried automatically into the invoice. Unbilled variations are one of the largest silent leaks we find in trade businesses.

Usually not. In most cases the platform can do the job and has been configured around old habits. We are honest when it genuinely cannot, and we will say so early instead of selling you a replacement you do not need.

We design capture around the way the work actually happens: minimum taps, offline tolerant, sensible defaults, no fields that exist only for the office. If people will not use it in the rain with gloves on, the data will not arrive, and everything downstream fails.

Almost always because parts are recorded in three places that never reconcile: the supplier invoice, the store or vehicle, and the job. We tie purchase, stock movement and job consumption to the same job reference, so what was bought, what was fitted and what was billed can be compared line by line.

Yes. We set up store and vehicle locations as real stock locations, with issues, returns, transfers and stock counts that site teams can actually complete. Once stock is trusted, over-ordering, emergency collections and write-offs drop noticeably.

We import supplier price files on a schedule, keep a cost history against each part, and separate cost from sell price so uplift rules are applied consistently. That means quotes are priced on current cost and margin reporting reflects what you actually paid.

We match supplier invoice lines to purchase orders and job references, then flag only the exceptions: unmatched deliveries, price variances, parts booked to no job. Finance reviews a short list instead of every line.

Yes, and this is normally the point of the whole exercise. Once labour hours, materials cost, contractor cost and revenue all resolve to the same job, you get job-level margin you can trust, then work type and contract level margin above it. That is where pricing and mix decisions start paying for the project.