01
Map
We talk about how the business sells, serves customers and operates. Then we list which systems, clouds and access exist, and which are critical to revenue.
You getA visual map of your environment and its most sensitive areas.
Method
Three steps. No surprises.
You know what will happen, when, and what it costs before we start. And your business keeps running throughout.
02
Test
With written authorization, we simulate real attacks and review configurations. Tests are scheduled with you so they don't disrupt sales or staff.
You getA report in business language, plus the technical detail for IT.
03
Strengthen
Priority 1✓
Priority 270%
Priority 330%
We fix what threatens the business most, first. We can make the fixes, support your IT team or vendor, then retest.
You getFixes in place, a retest and a plan for the months ahead.
In practice
What a typical project looks like
Timelines vary with the size of the environment. This is an example for a mid-sized business with an online store, an ERP and one main cloud.
Day 1
First conversation
30 minutes to understand the business and its concerns. Free.
Week 1
Proposal and authorization
Scope, timeline and price fixed in writing, together with the testing authorization.
Weeks 2–3
Mapping and testing
Work coordinated with your team, at times that don't get in the way of sales.
Week 4
Results presentation
One meeting with leadership and one with IT. Each in its own language.
After
Fixes and retest
Follow-up on fixes and confirmation that they worked.
Common questions
What business owners usually ask
How much does it cost?
It depends on the size of the environment and what makes sense to test. After the first conversation, you get a fixed-price proposal. No hourly billing and no surprises at the end. Many businesses start with a smaller assessment and expand later.
How long does it take?
A typical assessment takes two to four weeks, from first contact to results presentation. Larger or multi-cloud projects can take longer. The timeline is set in the proposal.
Will it stop my sales or systems?
That's not the goal, and we plan so it doesn't happen. More sensitive tests run outside peak hours, with an agreed emergency contact. If something looks risky, we stop and check with you before continuing.
I already have an IT team (or vendor). Does this still make sense?
Yes. We work with them, not instead of them. An outside view finds what people in the day-to-day don't have time to see, and your team gets a detailed technical plan to act on.
Is my data safe with you?
We sign a confidentiality agreement before starting. We access only what's necessary, read-only where possible, and evidence is deleted at the end of the project as agreed.
What happens after the project?
You keep the report, the plan and the retest of fixes. If you'd like, we can set up periodic reviews, for example every six months or before major changes.
Shall we start with the map?
The first conversation is free and already gives you a clear idea of where to start.