Nikzerodraft.studio

How I would start

Discovery, build, retainer

Three phases. Short paid discovery so the build is priced on facts, a fixed-price build with the first visible win early, then a retainer where I act as your technical lead. No prices on this page: the discovery produces the number.

01

Discovery

2 weeks

Map every source, define the ten numbers, design the build, return a fixed price.

  • Map every data source: QuickBooks, SPINS, each retailer portal, distributor exports, and what each co-packer actually sends (format, cadence, who sends it, how often it is late).
  • Define the ten numbers leadership actually needs, and which decision each one is late for today.
  • Design the warehouse and the first dashboards. Decide what stays in spreadsheets on purpose.
  • Return a fixed-price build quote with the scope written down. No hourly meter.
02

Build

6 to 10 weeks

Production and supply first, then sales and depletion, then self-serve. First visible win inside week 3.

  • Production and supply chain reporting first: WIP by co-packer and site, finished goods by DC, weeks of supply, plan vs actual.
  • Then the sales and depletion layer: SPINS, retailer portals and shipments in one place, so shipments and sell-through finally sit next to each other.
  • Then self-serve dashboards in Metabase behind your company Google login, so the team builds its own views.
  • Sync logs and a data freshness page from day one. Every number traces to its source.
03

Retainer

Monthly, ongoing

I stay on as your technical lead. New retailers, new sources, board pack automation, alerts, AI analysis.

  • New retailer or distributor? It is a new data source, wired in the same way.
  • Board pack automation: the numbers the President pulls by hand today, generated on a schedule.
  • Slack alerts on thresholds: weeks of supply, out-of-stocks, deductions above a limit.
  • AI analysis on top of the reporting: plain-English questions, narrative summaries, never a replacement for the numbers.

What gets built

The same path, every source

Whatever a partner sends lands here. New retailer, new co-packer, new portal: same five steps.

Animated pipeline: partner files, parsed and validated, Postgres warehouse, Metabase self-serve, Slack and AI on top

Principles

What does not change

You own the infrastructure and the data.
Your VPS, your Postgres, your logins. If we stop working together, everything keeps running.
Partners keep sending whatever they send today.
The system adapts to the co-packer, not the other way round.
Every number traces to its source.
A file, a row, a load time. That is how it survives a board question.
The team can self-serve.
Dashboards you can edit without me. I build the foundation, not a dependency.
Fixed price, no hourly meter.
Scope written down before the build starts. Changes are priced as changes.

To start

What I need from you

  • One example of a report you build by hand today. A screenshot is enough.
  • A list of your co-packers and what each one sends: format, cadence, who sends it.
  • Portal logins or a recent export from SPINS and one retailer portal.
  • 30 minutes with whoever owns production.

That is enough for me to make the discovery specific to your operation instead of generic.

Next step

Book a working session

Forty-five minutes. Bring one report you build by hand. I will show you what it looks like automated and what it takes to get there.

Book a working session