Layer 1 — Q1 of 5
What is the decision your organization is trying to get right?
Draft saved
Suluhu Studio · Design Intelligence for Africa
Kauli examines the decision in front of you — what you know, what you're assuming, and what you haven't asked yet.
20 minutes. No login. Specific to your organization.
Who this is for
Kauli works whether you are about to commit, already building, or questioning a direction that is already live. The framework it selects changes based on where you are.
Build Threshold
You have a direction and pressure to commit. Kauli tests whether the five conditions for proceeding are actually in place — before resources are committed.
Friction Map
Something is underperforming and the cause has not been located. Kauli maps where resistance is highest before any fix is designed or any resource is spent.
Signal Stack
You have data but cannot decide. Kauli separates what you know from what you believe — and names exactly which gap is producing the uncertainty.
How it works
Tell us about your organization
Sector, market, size. This calibrates every question that follows — the session is built for your context, not a generic template.
Five questions. Structured. Adaptive.
Kauli examines the decision, the stakes, your evidence, who bears the consequences, and what constraints you're working inside. It pushes back on thin answers.
Ten questions across five dimensions
Behavioral, economic, infrastructure, cultural, and systemic — the dimensions African market decisions most often miss.
A diagnostic brief, emailed to you
The real decision named. The framework selected. The structural findings that aren't visible from inside the organization.
The diagnostic frameworks
Friction Map
Something is underperforming. The cause hasn't been located. Maps resistance across five structural zones before any fix is designed.
Signal Stack
You have data but can't decide direction. Separates what you know from what you believe — and names which gap is producing the uncertainty.
Build Threshold
You're ready to move. Kauli tests whether the five conditions for proceeding are actually in place before you commit.
Not the right fit
Organizations that need a logo by next week
Teams optimizing primarily for cost, not decision quality
Everything already decided — execution only needed
Looking for someone to confirm what you already believe
20 minutes. No login required. Specific to your organization.
Profile information is used to calibrate the diagnostic. It is never shared.
Your answers are processed by Kauli to generate your diagnostic. Kauli does not use API inputs to train AI models. Session data is stored securely and only accessible to the Suluhu Studio team.
Before we begin
Review what to prepare below — or jump straight in.
◷ ~18–22 minutes from here
01
The decision you are facing
The specific determination to be made — not a goal or aspiration. Know the direction you are considering and the timeline you are working inside.
Example
"Whether to expand into Uganda in six months" not "we want to grow."
02
The cost of getting it wrong
The actual financial exposure, runway impact, or consequence. Not "it would be expensive" — the specific number or outcome if this goes wrong.
Example
"$400K burned with 14 months of runway left and our Series A window missed."
03
Your evidence and its source
What you know and how you know it. Know the difference between what you observed directly and what you concluded or assumed.
Example
"12 informal farmer conversations" is different from "a structured study with 200 users."
04
Who actually bears the consequences
Not the org chart — who feels a wrong decision most directly in their daily life or work. Know their names or roles before you start.
Example
"200 farmers in our first cohort who would lose credit access mid-season."
05
Your hard constraints
Non-negotiable limits — specific timelines, budget ceilings, unconfirmed dependencies, or capability gaps. Know at least two concrete ones.
Example
"Decision by end of May. Budget capped at $500K. Banking partner unconfirmed."
↗
One thing that will improve your output
Kauli pushes back on vague answers with a follow-up before moving on. This is not a test — it is how the diagnostic gets specific enough to be useful. Lean into the follow-ups. Kauli moves forward only — there is no back button. Answer as honestly as you can in the moment. Your full session with Suluhu is where you refine.
Tap to continue
Layer 1 — Q1 of 5
Reading your answer
Your diagnostic framework
Your enquiry has been sent. Someone from Suluhu Studio will be in touch shortly.
In the meantime, your diagnostic report is in your inbox.
The signal pattern from your session does not map cleanly to a single diagnostic framework. This is not unusual — it typically means the decision is at an inflection point where multiple forces are operating simultaneously.
A structured intake call with Suluhu Studio would allow us to navigate this together.
The Decision
The decision facing Shamba Credit — a collateral-free lending model built on satellite data and mobile money — is whether to commit to Uganda expansion within six months or hold until execution conditions are verified. If this goes wrong, Shamba Credit loses capital, delays its Series A, and exits a market mid-season — leaving hired agents without jobs and farmers without credit during active crop cycles.
Diagnostic Framework
BUILD THRESHOLD
For Shamba Credit's situation, Build Threshold examines whether the five conditions required to execute in Uganda — including a confirmed satellite data partner, legal registration, and a verified trust architecture — are actually met or only assumed to be.
Why This Framework
Shamba Credit is not choosing between strategic directions — it has a directional preference and is under pressure to commit to it. Build Threshold is most diagnostic here because three of its five readiness conditions are already visibly unresolved: the core underwriting infrastructure is unconfirmed, the behavioral evidence base consists of 12 informal conversations, and the Series A deadline may force a commitment before the data partner onboarding is complete.
Two Structural Findings
Infrastructure
Shamba Credit's satellite data gap and mobile money reliability in rural eastern Uganda share a single trigger point: harvest. The Kenya precedent took nine months from data partner engagement to first loan underwritten. Neither the data partnership nor a repayment fallback has been initiated for Uganda. The six-month investor timeline and the nine-month infrastructure reality cannot both be true.
System
Tier 4 registration under Uganda's Microfinance Institutions and Money Lenders Act has a conservative timeline of three to nine months — overlapping entirely with the planned July agent hire and September first-loan issuance. The nine-month scenario, which makes zero loans legally issuable in year one, has not been disclosed to investors. This is an undisclosed material risk inside an active Series A fundraise.
What's at Stake
A Build Threshold analysis for a decision of this size typically reveals 2–3 conditions that appear met but are not. In Shamba Credit's situation, the Tier 4 registration timeline is the most likely candidate — its nine-month ceiling sits entirely inside the planned execution window and has not been disclosed to investors.
KAULI
by Suluhu Studio
Your diagnostic is ready.