Environmental technologyBR Tech
Platform and digital presence for an environmental technology operation.
01Cases
Real problems. Decisions that changed course.
Strategy only matters when it changes what happens in the operation. Here are some of the problems we've faced at Northbound and throughout the partners' executive careers.
Selected projectsProblems, products and platforms we have built
Breadth before depth.
Different problems demand different products. Below, a selection of what we have built — before going deep into a single case.
Environmental technology
Data and customersCDP · Azzas 2154 Group
Unified customer view and segmentation across the group's brands.
Azzas 2154
Enterprise digital architecture
Platform for the architecture and executive understanding of the group's digital applications.
Altar Hub
Innovation and community
Portal for running an innovation hub and its resident companies.
Vokser
Services and agency
Digital platform for the operation and growth of an agency.
DANI
Digital product
A product for reading, memory and shared experience.
Klink Commerce
Commerce
Digital commerce experience for consumer electronics.
Zeniths
AI education
Platform for AI education and community.
WT1
Live, events and broadcasting
Institutional digital experience for a live and broadcasting company.
Meu LinkedIn Destravado
Professional development
Digital product for professional diagnosis and development.
Guia-se
Commercial CRM
Commercial CRM for a franchise operation.
Education · Mathematics
Education
Platform to follow students, assignments and corrections.
Tecnofábrica · Montreal
Enablement
Educational experience and a Product with AI workshop.
Featured case
Seven chapters · 07From isolated dashboards to an operating system for the company.
Dadri is where the whole thesis shows up: an enterprise operating system made of specialised Command Centers, connecting information, indicators, decision and execution under the same logic.
Here we leave breadth behind and go deep into a single project.
Seven chapters
- 01The context
- 02The thesis
- 03DADRI Operating System
- 04A common management language
- 05Inside the Command Centers
- 06From the executive view to operational detail
- 07What was built
01
Chapter 01
The context
Companies operate through different areas, systems, indicators, spreadsheets, tools and owners.
The problem is rarely a lack of information. It is the distance between seeing a number and someone owning a decision about it. Each layer of that chain usually lives somewhere else.
What stays fragmented
- 01Information
- 02Interpretation
- 03Decision
- 04Ownership
- 05Execution
02
Chapter 02
The thesis
What if the company had its own operating system?
The proposal was to build an executive and operational layer able to organise different domains of the company under one logic: the same indicators, the same health reading, the same path from exception to action plan.
Not one more report. A way of operating.
03
Chapter 03
DADRI Operating System
Each Command Center is an independent application inside the same ecosystem. One domain per application, one operational logic for all of them.
The reading
- →Multiple domains
- →One operational logic
- →One management language
Command Centers
Commerce
E-commerce performance, sales, customers and operation
People
People, structure, development and succession
Partners
Partners, contracts, SLAs, cost and risk
Inventory
Stock, receiving, storage and shipping
Finance
Cash, result, budget and financial risk
Product Lifecycle
Collections, development, materials and launch
Wholesale
Wholesale, reps, orders and credit
CRM
Segments, RFM, retention and journeys
Customer Service
Service, queues and resolution
Legal & Contracts
Contracts, obligations, governance and legal risk
Projects / PMO
Portfolio, roadmap, deliveries and dependencies
04
Chapter 04
A common management language
Every Command Center follows the same path. The domain changes, the logic does not.
- 01DataOne source per domain
- 02IndicatorsTarget, previous period and status
- 03Health scoresPillars with explicit weight and rule
- 04Alerts and exceptionsWhatever breaks the rule surfaces
- 05DecisionsWhat has to be decided now
- 06OwnersA name attached to the decision
- 07Action plansDeadline and follow-up
05
Chapter 05
Inside the Command Centers
The same grammar applied to completely different domains.
E-commerce
Commerce Command Center
Executive cockpit for e-commerce: period result, targets, comparison with the previous period and overall health on a single reading plane.
Stock and logistics
Inventory Command Center
Exception-based reading of the stock operation. Every indicator carries target, comparison and the reason behind its status.
Finance
Finance Command Center
Cash, result, budget and financial risk consolidated, with scenario and projection side by side.
Product
Product Lifecycle Command Center
The full product cycle — from idea to commercial launch — with planned, actual and projected always together.
Partners
Partner Command Center
Cost, performance, risk and contract read together, with the partners that demand a decision in the foreground.
Wholesale
Wholesale Command Center
Commercial pipeline, reps, credit and default under the same target and forecast reading.
Customers
CRM · RFM
The base classified by recency, frequency and value, with a recommended action per classification.
Legal
Legal & Contracts
Contract portfolio with obligations, expiry, notice period, owner and risk visible in the same table.
Portfolio
Projects / PMO
Portfolio roadmap with milestones, cross dependencies and critical windows by programme.
06
Chapter 06
From the executive view to operational detail
The same architecture allows you to leave the consolidated view of the company and land exactly on the domain where a problem exists.
- Company
- Command Center
- Indicator
- Exception
- Owner
- Action
No step requires switching tools or vocabulary. The path is always the same; only the depth changes.
07
Chapter 07
What was built
A product architecture able to turn different company functions into specialised Command Centers, while preserving one experience, one management language and one decision logic.
Product elements
- Operating System
- Specialised Command Centers
- Executive layer
- Indicators and health scores
- Exception management
- Alerts
- Governance
- Action plans
- Operational views
- Expandable architecture
The screens shown use fictional demonstration data.
Track record
The experience that brought Northbound here.
What the Dadri case shows did not appear now. It is the consequence of years building and running digital products, platforms and organisations at scale.
- Azzas 2154
- ≈ R$1.5B
- digital GMV across the ecosystem during the period
- Reserva
- 8% → 35%
- approximate app share of digital over the period
- Azzas 2154 · 2023–2026
- ≈ 11 teams
- technology structure organised in teams, evolving into domains with leadership and post-merger integration
- DADRI Commerce
- ≈ R$412K
- Net revenue in the period analysed; the economic reading showed the final result squeezed to ≈ R$3K.
Also at
Farm · Animale · Maria Filó · Cris Barros · NV · Hering · Reserva · Oficina · Off Premium · Santander · Banespa · Banco Real · App4Hash · Buscapé · Polishop · C&A · Lojas Renner · TIVIT · Telefônica · Salesforce · iFood
Operation figures for the period. Not attributed to a single person or initiative. Prior professional experience of the partners and leadership team. Inclusion in this section does not represent a commercial relationship with Northbound.
What we do
We turn business complexity into operating systems.
Technology is a consequence. First we understand how the company needs to operate.
Architecture comes after the decision. That is why we start with how your operation needs to read, decide and execute.
Northbound engagements
Where is the complexity of your operation keeping the company from deciding or executing better?
Tell us what is happening.
Next step
Qual problema precisa sair da mesa?
Vinte minutos, sem compromisso. Se preferir escrever, o formulário ao lado chega direto para nós.