Two revenue numbers.
One meeting.
Month-end runs late. Reports take manual work. Every new question becomes another reconciliation project.
Reporting slows decisions.The company behind NorthTrace
Signal NorthData, Analytics & AI Advisory
Turn fragmented data into trusted decisions.
Data, Analytics, and AI AdvisoryOne number.
One number.
Everyone aligned.
For mid-market companies running multiple systems, where consolidated reporting is slow, manual, and quietly mistrusted.
One number, agreed upon by everyone who reports it.
From fragmented to alignedThe target state
ERP AEntity 01
ERP BEntity 02
ERP CEntity 03
One shared data model
Common entities. Agreed definitions. Clear ownership.
CustomerProductCalendarOrganization
One number. A shared understanding.Reporting your business can stand behind.
Illustrative architecture · Designed around your systems
Designed for the complexity you already have
Multiple ERPsMulti-entity businessesShared metric definitionsBuild-ready architecture
The real problemYour systems are connected.
Your systems are connected.
Are your definitions?
The friction often starts before the dashboard. It starts with what your data means.
Two revenue numbers.
The same entity.
Different meanings.
Customers, products, calendars, and hierarchies differ across systems. Metrics lack written definitions and clear owners.
The model is unresolved.New platforms.
The same arguments.
Tooling gets bought before the model is settled. The reconciliation work arrives later, during a more expensive build.
Architecture needs to come first.The BlueprintA shared model.
A shared model.
A practical way forward.
We specify what gets built, prove it on your real data, and give your team or vendor a plan they can build from.
The architecture your multi-entity business runs on.
Six concrete deliverables, with one contested metric modelled and reconciled end to end. Design grounded in your actual systems.
10 weeksSix named checkpoints
2–3Source systems in standard scope
6Build-ready deliverables
1Metric proven on real data
01 Conformed dimension design
For every shared entity—customer, product, calendar, organization, vendor, and location—the master definition, source-of-truth ranking, matching logic, survivorship rules, and treatment of change over time.
02 Fact design & grain decisions
Which fact tables exist, at what grain, and why. How transactions from different ERPs conform to a shared structure, and where they deliberately remain distinct with a documented business rationale.
03 Source-to-target mapping
Every field and source mapped to the target model, with transformation logic in business terms. Missing data, unreliable fields, and process changes are named explicitly.
04 Semantic layer specification
Every metric defined in writing, with an owner: calculation logic, filters, time intelligence, and roll-up hierarchies. A definitions register your team can maintain.
05 Platform & architecture recommendation
Target layers, ingestion patterns, orchestration, and refresh cadence, with total cost of ownership. The option to keep what you have is costed alongside the alternatives.
06 Phased build plan
Three to five delivery phases, with effort estimates in person-weeks and the skills needed for each. Every phase ends in something the business can use. Written so a vendor can bid against it.
Scope: design, specification, and one proof-of-concept metric. Production pipelines and full platform implementation are separate engagements.
The number has to reconcile.
We pick your most contested metric—often consolidated revenue—and model it across your actual ERPs. Then we show it reconciling. The proof build is part of every Blueprint, because the design needs to survive contact with your data.
The delivery pathTen weeks.
Ten weeks.
Six clear checkpoints.
A defined sequence from discovery to a demonstrated model and a documented handoff.
- Weeks 1–2
Deep discovery
Schema-level work and focused sessions with your system owners.
- Weeks 3–4
Dimension design
Shared entities, matching rules, and workshops to resolve conflicts.
- Weeks 5–6
Facts & mapping
Grain decisions, source-to-target mapping, and gap analysis.
- Weeks 7–8
The proof build
One metric, modelled end to end and reconciled on your data.
- Week 9
Platform & plan
Architecture, total cost of ownership, and delivery sequencing.
- Week 10
Readout & handoff
Documentation, leadership presentation, and a build-ready plan.
Ways to work togetherThe right engagement
The right engagement
for the decision ahead.
Start with clarity. Design the target state. Keep the implementation aligned.
The assessment
A focused read of where reporting breaks: systems, ownership, and definitions. You leave with a recommendation, including when the answer is to do nothing yet.
Scoped per engagement
Fixed scope, agreed before we start.
Discuss an assessmentThe Blueprint
The target model, mappings, definitions, architecture, and build plan. One metric proven on real data. Ten weeks from discovery to handoff.
$45,000 standard
Two to three source systems.
$60,000+ for four or more systems, multiple entities, or complex hierarchies.
40% kickoff / 30% midpoint / 30% delivery.
The retainer
Keep definitions, vendor decisions, and delivery aligned with the design. A consistent owner for the roadmap between funding cycles.
$6,000 / month
Advisory or build supervision.
$9,000/month including build vendor management.
Your team builds it.
We can review delivery against the specification before it becomes load-bearing.
A vendor builds it.
We can run selection against the specification and manage delivery on your side of the table.
Nobody builds it yet.
You own the design. We can keep the roadmap current until the business is ready.
How we workClear thinking.
Clear thinking.
Practical architecture.
The work should make your next decision easier—and your next investment better informed.
We tell you when you don’t need us.
If the problem is process or ownership rather than architecture—or there’s no one to build the design—we say so before you spend.
We design for the company you are.
The target state should be reachable. Streaming, real-time systems, and complex patterns belong only where the business needs them.
The platform recommendation is honest.
We take no vendor fees. We cost the option where you buy nothing new. Sometimes that is the right recommendation.
The scope boundary is written down.
Design, specification, and one proof metric. Production build work is scoped separately so the engagement stays clear.
Gaps get named.
If a number cannot be reported until someone starts entering the data, leadership hears that finding directly.
Value lands in phases.
The build plan is sequenced around usable business outcomes, so progress is visible before the entire platform is finished.
Behind Signal NorthEnterprise experience.
Enterprise experience.
Direct access.
Zack Gregory
Founder · Data, Analytics, and AI Advisory
I started Signal North for companies with multiple ERPs, reports that take too long, and numbers nobody quite agrees on.
My background spans data, analytics, engineering leadership, and complex technology programs—including leading a data pipeline engineering team supporting Meta’s Ray-Ban and Oakley smart glasses through Affirma, alongside experience at Amazon and Microsoft.
The goal is straightforward: bring that rigor to mid-market companies, with an architecture they can understand, fund, and build.
15+ yearsData & technology experience
Multi-ERPEnterprise model design
Founder-ledDirect collaboration
Organizations mentioned describe prior professional experience, not Signal North clients or endorsements.
Start a conversationBring us your most
Bring us your most
argued-about number.
Tell us which systems you run, what leadership needs to know, and what’s getting in the way. We’ll start with a conversation.
Let’s talk hello@signalnorthdata.comA 20-minute first conversation. No pitch deck required.