Project Zero
We do not start with ideas.We start by listening.
Every great software product begins with understanding a real business problem.
Project Zero is our ongoing research initiative, where business owners openly share the operational frustrations, repetitive work, and bottlenecks they face every day.
Tell us what is making your business harder to run and you will receive a free Business Friction Snapshot: a first-pass look at what may be causing it, what it may be costing you, and three practical things you could try next.
Every great product begins with an honest conversation. We would love to hear yours.
Project Zero is a research initiative by Dunjeestudios. This is not our company website. It is where we listen, before we decide what is worth building.
Why we’re listening.
Software fails when it is built for a problem nobody actually has. Listening first is the cheapest way we know to avoid that, and it is the one part of the process we refuse to shorten.
Because the problem comes first
We would rather spend a month understanding your work than a year building the wrong answer to it.
Because you are not a lead
Project Zero is research. There is no pitch waiting at the end of it, and no sales call unless you ask for one.
Because you get something back
Contributors can hear what we learn, and early contributors get first access to what we build from validated problems.
The initiative
What is Project Zero?
Project Zero is Dunjeestudios’ ongoing research initiative. Before we build software, we listen.
We work directly with business owners to understand recurring operational problems, identify patterns, and validate the opportunities worth solving.
It is not a one-way exchange. Describe a problem and we will give you a free Business Friction Snapshot in return: a structured first look at what may be happening, what it may be costing you, and what you could try next. No charge, no call, no obligation.
The result is software grounded in evidence rather than assumptions.
Why zero
Zero is the step before the first one. It is the part almost everybody skips.
Our approach
Three habits, held to strictly.
They are simple to describe and difficult to keep. Most of the discipline is in refusing to move on before the previous one is finished.
Listen
We begin by understanding businesses before writing a single line of code. No pitch, no demo, no assumptions carried in from the last project.
Discover
We identify recurring patterns and test whether they hold. One story is an anecdote. Repeated signals can reveal a problem worth investigating. Validation tells us whether it is worth solving.
Build
Only validated problems become products. Everything else stays in the notes, where it costs nobody anything.
The process
What happens after you share.
Six steps. The first two are yours, and the second happens immediately.
Share
You tell us what is making running your business harder than it should be.
Understand
You receive a free Business Friction Snapshot straight away: what the problem may be, what it may be costing you, and three things you could try.
Listen
We collect experiences without assuming the answer, and look across them for problems that recur.
Validate
Repeated signals are investigated to determine whether the problem is genuinely worth solving.
Build
Only when the evidence supports it do we build toward a solution.
Learn
We learn from what happens next, and contributors may hear what we discovered.
And we close the loop.
Your experience does not simply disappear into a database. As we learn from the problems people share, we may come back to contributors with what we have found and where the research is leading.
If a validated problem leads to something we build, contributors may be invited to experience it early.
What we are hearing
Business frustrations we are hearing.
The patterns that keep surfacing, in the words of the people living with them. This section grows as Project Zero does.
“We spend hours manually following up with leads.”
Marketing agencyIllustrative
“We answer the same customer questions every single day.”
EducationIllustrative
“This approval process slows everything down.”
Creative studioIllustrative
Illustrative, until the first submissions come in. Nothing here is attributed to a real business without permission.
Most software fails long before anyone writes it. It fails in the moment someone decides what to build.
The studio
Who is behind this.
Dunjeestudios is an innovation studio. Project Zero is how our work begins, and these are the four things we do once it does.
- Discovery research
- Structured interviews, process mapping, and field observation that turn a vague frustration into a documented, measurable problem.
- Product design
- Interfaces that reduce the number of decisions a person has to make. Clarity first, and nothing on the screen that is not doing work.
- Engineering
- Web and internal software built to be maintained. Sensible architecture, honest documentation, and a handover you could actually use.
- Ongoing partnership
- Measurement, iteration, and the occasional recommendation to stop. We would rather be useful to you than busy on your budget.
Principles
What we hold to.
Evidence before enthusiasm.
The people doing the work know the most about it.
Simplicity is expensive. We pay for it anyway.
A smaller product, finished, beats a larger one imagined.
If we cannot explain it plainly, we do not yet understand it.
Say no early, and say why.
Website job
Our job is simple.
We listen to the people running businesses.
- Listen
- Find the pattern
- Validate
- Build
- What is this?
Project Zero is a research initiative by Dunjeestudios. We listen to real business problems before deciding what to build.
- Why should I care?
Because the problem frustrating you may not be yours alone.
What feels like an isolated headache could be a pattern shared by hundreds of businesses.
- What do you have to do?
Vent. Tell us what is frustrating you, in your own words.
No pitch deck. No demo. No sales call. Just tell us what is not working.
- What happens next?
You receive your free Business Friction Snapshot on the next screen: a structured first look at what may be happening, what it may be costing you, and three practical actions you could try.
Then we listen. We study what we are hearing, look for recurring patterns, and investigate whether there is a meaningful problem worth solving.
- And if the evidence says it is worth solving?
We build toward a solution.
- Will you build something for my problem?
Not every problem becomes a product. Some need better processes, different people, training, or an operational change rather than software.
We follow the evidence rather than forcing every problem into an app. Working out what kind of problem you actually have is part of the job.
Vent form
Vent.
Vent first. Understand the friction next.
Tell us what is making your business harder to run.
Describe a real problem in your own words. You do not need to polish it, you do not need the right terminology, and you do not need to know what the solution should be.
Whether you run a real estate company, a restaurant, a construction business, a fashion label, a clinic, an agency, a shop, or something else entirely, the process is the same: describe one recurring problem and we will help you make it clearer.
You are not signing up for anything. We are not selling anything. This is research, and you can ask us to delete your response at any time.
What you get back
When you submit, we turn your answers into a free Business Friction Snapshot. It appears on the next screen, straight away.
- What the problem may be, and where the friction appears to sit
- What may be happening underneath it
- What it may be costing you, based on what you told us
- Three practical actions you could try without buying anything
- One thing to measure so you can tell whether it is improving
- A plain account of what we still do not know
This is not a sales call and it is not a consultancy report. It is a structured first attempt to make the problem clearer.
- What am I doing?
- Telling us about a real problem you are experiencing in your business.
- Why?
- Because useful products should begin with real problems, not assumptions about what businesses need.
- What happens to it?
- We study it alongside others, look for patterns that recur, and investigate whether a problem is worth solving.
You can also just write to us at hello@dunjeestudios.com.