About Data Dune
Why trust us with the number
Data Dune helps growth-stage teams build reporting their leadership can trust. This page is here to show the proof before we ask for a call.
Founder
A named person, not a sales desk
Igor Garlowski
Founder, Data Dune
Data Dune was founded by Igor Garlowski after seeing the same problem repeat: teams had dashboards, but not one trusted definition of the numbers underneath them.
The work is deliberately practical. We agree what a number means, build the data layer that produces it, and hand it over so the client team can run it without us.
We are small by design. Clients work close to the person responsible for the architecture, the delivery and the handover.
Proof we can make visible
Every claim on this page is named, dated or checkable. Nothing here rests on us saying it.
- 2022
- Running since
- 11
- Named client references
- 96%
- Delivered within scope
- Tableau
- Ambassador and certified
Named people, not anonymous praise
These quotes come from people who worked with us directly.
I highly recommend Igor for his exceptional skills in Tableau, SQL, ELT and his quick ability to pickup new things. His expertise in these areas, combined with his strong analytical mindset, makes him an invaluable asset in any data-driven project.
Igor consistently delivers high-quality work and demonstrates a strong commitment to continuous learning and improvement. He is a dedicated professional with a passion for leveraging data to drive actionable insights. It has been a pleasure and privilege to work with Igor, hope we will continue to work together for many more years.
Vinay Katdare
Tech Lead, NewPage Solutions
He has contributed above expectations to the service area he works in.
Not only has he demonstrated deep domain knowledge around Tableau, data visualization and integration, but he also provides frequent input on how the team can improve service delivery and increase value for internal customers.
Dick Olsson
Director, Principal Engineering Lead, Pfizer
It was my huge pleasure to work with Igor on a data project where he was delivering different dashboards over a few weeks remotely. The scope of the work was constantly changing but thanks to Igor's professional approach he mastered it perfectly.
His strength: organized, clear, on top of things, communicates well, proactive and involves stakeholders when necessary. Its a great feeling to know that your projects are in good hands - in those of Igor.
Zdenka de Booij
Account Executive, InterWorks
What trust means here
Trust is built into how the work runs
We cannot ask a team to trust a dashboard if the delivery behind it is vague. The engagement has to be clear as well.
We start with one disputed number
A real metric exposes the definitions, systems and ownership problems faster than a discovery deck.
We write down the trade-offs
Cost, speed, governance and maintenance are design choices. We put those choices in front of the client while there is still time to change them.
We show the work as it changes
Clients see progress during the build, not just a polished handover at the end. That makes corrections cheaper and trust easier.
We leave the route map behind
Documentation, training and ownership are part of the scope. The aim is that the client team can run the work without us.
How an engagement earns confidence
A short, visible path from first conversation to handover. No theatre.
Fit call
We talk about the number that is not trusted and say if we are the wrong fit.
Written scope
You get the problem, approach, trade-offs and price in writing before work starts.
Open build
We work in the tools and rhythm agreed with you, with visible progress and clear decisions.
Handover
We leave documentation, training and checks so your team can own the result.
Questions buyers usually ask
Is Data Dune only Igor?
Data Dune is founder-led and stays small on purpose. Regular consultants and contractors join specific engagements, so the team scales without growing headcount. If a project needs extra hands, the scope should say who is involved and why.
Can you prove the Tableau credentials?
Yes. Every Ambassador badge shown on this site links to Tableau's own community page, where anyone can confirm it.
Do you work with regulated teams?
Yes, where the scope and controls are clear. Named regulated examples should only be used where permission is already public.
What should we prepare before a call?
Bring one number people argue about, where it appears, and who uses it. That is enough for a useful first conversation.
Next step
Bring the number nobody trusts
We will talk through what is wrong, what it would take to fix it, and whether we should help.
Thirty minutes, straight to the problem. No deck, no pitch, and a written summary afterwards either way.