The ten questions that come up before every project
If yours is not here, ask it on the call — or email it and you will get a written answer without a sales conversation attached.
Send the file, or describe what you need, through the contact form, email or WhatsApp. You will get a written scope and a fixed price — usually within one business day. Nothing is billed until you approve it.
By project, on a fixed price agreed before work begins. Hourly billing rewards slow work, and it makes budgeting impossible for you. Retainer clients buy a monthly block of hours instead.
We sign NDAs before receiving files, restrict access to the specialists on your project, and delete working copies on request once a project closes. For very sensitive workbooks we can work on a version where values are replaced but structure is intact.
Single-file repairs usually come back the same working day. Dashboards and models typically run one to three weeks depending on scope. If you have a hard deadline, say so up front — we will tell you honestly whether it is achievable.
Every project includes two revision rounds against the agreed scope. If the delivered file does not do what the scope said it would, we keep working until it does, at no extra charge.
Excel 2016 onward on Windows, Microsoft 365, Excel Online and Excel for Mac. Tell us your version before we quote, because it changes which functions and automation methods are available to us.
Yes. Blocked macros, no external add-ins, locked-down file sharing — all common, all workable. Power Query, Office Scripts and native formulas cover most automation without triggering a policy exception.
Yes. The team spans multiple time zones and we work with clients across the US, UK, Europe, the Middle East and Australia. Calls are scheduled in your working hours.
A specialist from our team of 13, matched to the job — a data specialist for modelling and analysis, a tech specialist for automation and interface work. Jay reviews every deliverable before it goes back to you.
That is a large share of what we do. We document what the existing file does, tell you what is fragile, and give you the choice between repairing in place and rebuilding on a cleaner structure.
Two things worth knowing before you write to us
A messy file is not a problem
You do not need to tidy it before sending. The mess is diagnostic — it tells us how the file is actually used, which a cleaned-up version would hide.
You do not need to know the solution
Describe what is slow, wrong or fragile. Naming the right tool is our job, and we would rather you did not pre-commit to one.
Ask the question directly
Twenty minutes, no obligation, and a straight answer on whether this is work worth paying for.