Context first. We don't enter projects blind.
Same AI model, 97% failure with only a task description — near-100% success with rich context. Context isn't a bonus. It's the deciding variable. Terrain is the layer that reads your ground before Seven Peaks builds on it.
Two layers, built before we meet and enriched every day after.
Customer DNA is a context profile for every client, in two layers:
The public layer — built from open sources before we meet: websites, registries, industry data, technology fingerprint, press, social, market position. Specialised agents do this: research agent, competitor watcher, news agent, qualification agent, summarisation agent, matching agent, recommendation agent. Connectors include web scraping, API integrations, CRM hooks, meeting-capture, document ingest, email parsing, third-party data — the hidden sources that separate us from competitors.
The internal layer — what the relationship reveals: meeting notes, internal priorities, the actual truth behind the façade, political realities, real decision history. Built over time, inside the engagement.
Customer DNA is what we know about you. Client Memory is the mechanism that keeps it alive between sales, delivery, and every iteration after — so context never dies when a contract signs or a phase ends.
Architecture grounded in context, not whiteboards.
What a classic consultancy calls konsept og arkitektur or concept & architecture lives inside Terrain. That's not a demotion — it's an upgrade. Architecture decisions made in a one-week whiteboard workshop with generic industry reports beat no architecture. But architecture decisions grounded in your Customer DNA, your actual constraints, your real decision history, and continuously updated market intelligence beat the whiteboard every time.
What we produce inside Terrain:
- System landscape and integration map, built from your real stack, not your slideware
- Target architecture alternatives scored against your constraints, not against generic best practice
- Prioritisation logic (what to do first, what to defer, what to stop) grounded in Customer DNA
- Shield Layer 2 inputs — the customer-specific compliance and governance rules that must hold
Architecture without context is speculation. Architecture inside Terrain is a decision grounded in everything the relationship reveals.
A product in pilot, not just a method.
Terrain isn't only the foundation of Seven Peaks' method — it's a product that can stand on its own. We use Terrain ourselves for prospect work, lead qualification, customer intelligence, and continuous context-building. It's currently in active pilot with sales-and-meeting-booking partner Brave AS: the test is whether Terrain gives Brave better preparation, better talking points, and higher hit rates.
When Terrain is used as a standalone product, the client is the Sales company — the organisation using Terrain to find leads. Inside Seven Peaks we call our own profile "Seven Peaks-profilen." When we speak to other Terrain users, we call theirs "Sales company."
Gains for the engagement.
- Richer Customer DNA before the contract — not "discovery" that starts when the kickoff happens
- Stronger context entering Foundry — so delivery starts at kilometre 20, not at kilometre zero
- No context loss when projects change phase or team
- Ongoing market, competitor, and regulatory intelligence that continues after launch (via Signals Lag B)