MVP FastPass

How it works

Start from wherever you’re at.

Every engagement starts with the same question: do you already have a data warehouse, or does one need to be built? If you have one, I build the reporting straight on top of it. If you don’t, I build the warehouse and ETL first — or on their own, if the warehouse is all you need.

Path A

You already have a data warehouse

Turn the data you already have into clear, actionable reports built around your business. I build on your existing data warehouse, starting with your first working report — so you get more value from the foundation you’ve already invested in.

  1. 1

    Connect. Secure connection to your warehouse, using a service account you control.

  2. 2

    Model. The data your report needs, organized and documented so the next report can reuse it.

  3. 3

    Build. Visuals, grids, filters, permissions. A first look 1–2 weeks after I’m connected.

Typical timeline: A first look at your first report 1–2 weeks after I’m connected to your data.

Path B

You need a warehouse and ETL

I build a data warehouse sized to your needs, with automated data pipelines that bring together information from your ERP, CRM and other systems. With your data organized and ready for reporting, I can build your reporting solution as described in Path A, or hand the warehouse over to your team for use with your own BI tools.

  1. 1

    Warehouse. Set up in your cloud account, so it is yours from the first day.

  2. 2

    ETL. Scheduled pipelines from each source, with monitoring so you know when a load fails.

  3. 3

    Organize, then report. Your data is organized and documented either way. If you want reporting, it’s built on top at the same speed.

Typical timeline: 2–4 weeks for the warehouse and ETL. If reporting follows, a first look at your first report 1–2 weeks after that.

Under the hood

Sources in, reports out, and a way back.

  1. Sources

    Your systems

    ERPs · Payroll · CRMs · Custom systems · Spreadsheets · Exports

  2. ETL

    Pipelines

    Scheduled loads, cleansing, monitoring

  3. Warehouse

    Reporting datasets

    Modeled views · history · custom data tables

  4. Reports

    MVP FastPass app

    Visuals · grids · filters · editable fields · permissions

Orange arrow: editable reports. Notes, flags, and custom fields entered in the report are stored in the warehouse, with permissions.

How the warehouse and pipelines are built

Experience integrating data from

ERP

  • Vista Viewpoint
  • CMiC
  • JDE
  • Epicor
  • Coins
  • NetSuite
  • Dynamics
  • FACS

CRM / Other

  • Zoho
  • FreshDesk
  • Compass
  • Lasso
  • ADP
  • Concur

Don’t see yours? If it has a database, an API or an export, I can pull from it.

A typical first engagement

What the first few weeks look like.

Week 1

Connect & sketch

Access is set up and the datasets are identified and modeled. You see a first sketch of the report by the end of the week.

Week 2

Your first look

Real data, real visuals, real grid. You and the people who'll use it click through it and tell me what's wrong.

Week 3

Refine & secure

Permissions, exports, scheduled refresh and editable fields. The edge cases get handled.

Week 4+

Live, and iterating

The old spreadsheet gets retired. Changes take days. The next report starts from what's already built.

Weeks are counted from when I’m connected to your data. Where a warehouse and ETL have to be built first, that comes ahead of Week 1 and adds 2–4 weeks. Timelines depend on how quickly I can get access to the systems, data and requirements needed to begin working.

Not sure which path you’re on? That’s what the scoping call is for.