Pushbuild

Spreadsheets and dashboards packages

Three ways to start, each with a clear deliverable. These are examples to show the shape of the work; your project gets its own written scope, with cost and timing, before anything starts.

Ask for a scopeBack to spreadsheets and dashboards

The packages

Pick the one closest to what you need. Anything in between is fine; the scope is written around you.

Package 1

Automate one report

For: A team that rebuilds the same report by hand.

The report you build every week, refreshed with one click or on a schedule.

You get

  • The report rebuilt to refresh from its sources
  • Checks that flag missing or odd data
  • A refresh button or a scheduled run
  • Notes on how it works

What we need from you

  • The current report and where its data comes from
  • Read access to those sources
Ask for a scope

Package 2

Business dashboard

For: Owners and managers who want one set of numbers.

A dashboard of the measures you run the business on, fed from your systems.

You get

  • Measures defined and agreed in writing
  • Data pulled from CRM, accounting or operations
  • A dashboard in Looker Studio, Power BI or Sheets
  • A weekly summary email

What we need from you

  • The questions you want answered
  • Access to the systems the numbers live in
Ask for a scope

Package 3

Spreadsheet to system

For: A business whose key workbook has outgrown itself.

The workbook that runs the business turned into a shared tool with forms, roles and automation.

You get

  • Data moved into a proper database (Airtable, Sheets or Postgres)
  • Entry forms and role-based views
  • Automations for the repetitive steps
  • Reports rebuilt on the new data

What we need from you

  • The workbook and how it is used today
  • Who enters, edits and reads what
Ask for a scope

How we work

You know what you're getting before work begins, and you see it working at every milestone.

  1. You describe it

    Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.

  2. A written scope

    We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.

  3. Milestones you review

    The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.

  4. Handover and a 30-day fix window

    You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.

What shapes the scope

  • Which package is closest, and what changes
  • How many systems, documents or users are involved
  • Access to the tools it connects to
  • How quickly we get answers to the scope questions

Always included

  • A written scope before work starts
  • Milestones you review and sign off
  • Documentation and a walkthrough at handover
  • A 30-day window for fixes, at no charge

Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See products we've built.

Tell us what you need built.

Tell us which package is closest and what's different about your case. We reply with questions or a written scope.

hello@pushbuild.com

(617) 299-8887