# data · data.sql

Excel & VBA Analysis

Excel and VBA work — pivot models, macros and dashboards built to spec.

ExcelVBA

An Excel submission that's one impenetrable formula in cell Z99 is hard to mark and harder to defend. We build with named ranges and auditable formulas, comment any VBA, and leave the workbook open so a marker — or you, in a viva — can see exactly how each number was produced.

What you get

  • Formulas built to be auditable, not a black-box single cell
  • Pivot tables and charts that update cleanly when data refreshes
  • VBA macros commented so a marker can follow the logic
  • Named ranges used instead of hardcoded cell references
  • A clean, unlocked workbook — no hidden sheets hiding the work
  • Tested against your brief's sample data before delivery

What to send first

  • The dataset (or a sample of it) and where it came from
  • The questions the analysis has to answer, or the model's target
  • Required tools — SQL dialect, Python libraries, R, Excel version
  • The report format: notebook, PDF write-up, dashboard or slides

How it runs

  1. 01

    Send the spec

    The brief, the rubric, any starter code and the versions your marker uses. A photo of the PDF is fine to begin with.

  2. 02

    Scope and quote in writing

    We read it properly, ask what is unclear, and confirm a fixed price and delivery date. A small advance confirms the order.

  3. 03

    Build against the brief

    Work is tracked task by task against the spec. Longer projects are split into milestones you can review as they land.

  4. 04

    Tested handover

    A repo that installs from a README, run against your test cases, with the write-up if your rubric asks for one.

  5. 05

    Fixes and walkthrough

    One round of fixes if a marker flags something, and a walkthrough of how it works so you can explain it.

Excel & VBA Analysis: common questions

The notebook or scripts that produced every number, so the analysis can be re-run end to end. Results pasted into a report without the code behind them are hard to defend.

No. Data is used only for your task, never shared or reused, and deleted on request once the work is signed off.

It depends on the scope of the brief, the stack and the deadline. Send the spec on WhatsApp and you get a fixed price and delivery date in writing before any work starts — no hourly meter.

Turnaround depends on scope and is agreed with the quote. Tell us the real deadline, including the timezone, and we will say honestly whether it is workable before you commit.

./send-brief

Send your brief.

Paste the excel & vba analysis brief into WhatsApp — the message already names the service. Scope and price come back in writing.