Internal team whiteboard • 2026-05-21 • SHUR IQ
This was the session where we stopped describing what SHUR IQ could be and started agreeing on what it is. June 26 was the date mentioned in the room; the launch sequence has since landed on a two-step: the June 29 weekly stack-rank report goes out first (off the 6am Monday daily insight), then two weeks of billing and subscription-tier fine-tuning, culminating in the full-scale launch on July 13. Christine is writing the intake. Alex is building the visual system. The knowledge graph is on its way from 80,000 nodes to a million by end of June, and that's what makes the rest of this defensible. The Reffer JV still doesn't have a home in the product stack — that's the thing next week needs to settle.
We moved past intake and into active co-strategy. Nuri framed the trunk-and-branches architecture for a templatized core product with bespoke modules; Christine pressure-tested the buyer for the Brand Power Score / Structural Advantage Score; Jonny grounded the conversation in the knowledge graph as our durable IP.
The enterprise launch is sequenced in two steps. The June 29 weekly stack-rank report drops first, off the 6am Monday daily insight. The full-scale launch lands on July 13 after two weeks of billing and subscription-tier fine-tuning. June 26 was the date mentioned in the room. Manual high-touch delivery first, automation following. The agency partnership channel and the API + licensing layer are explicit revenue strands alongside direct client subscription.
What ships next is a tier-aware intake template (Christine), a visual system that scales across client size (Alex), and the first enterprise engagement delivered manually so we can watch what breaks.
"It has to be templatized. We don't have an opportunity to ask questions. The premium that starts to be paid when a client says, okay, this is great, we'd love for you to get back into our data — we can do some onboarding and ask some questions really specifically."— Nuri Djavit · 14:12 / 16:34
Held the long view. Made the case that our job is to keep sharpening the brand brain — "how much sharper can we make this brain" — rather than chase every adjacent product. Gated agency partnerships, design-system tiering, and the role of bespoke creative.
Drove the templatization argument. Introduced the trunk-and-branches metaphor for the main product plus client-specific modules. Owned the Structural Advantage Score / Brand Power Score positioning for PE and CMO buyers.
Anchored the agency side. Pushed back early on full templatization — "our approach does tend to bespoke" — and named where the Shur agency feeds enterprise engagements. Will draft intake templates per client tier.
Played the buyer and the founder. Used the pitch deck product to surface what a startup needs from intake, asked the API-inside-Claude question first, and volunteered to write the startup intake questionnaire.
Grounded every product strand in the underlying knowledge graph. Surfaced the 80K-to-1M node milestone, the API-as-separate-revenue thesis, and the engagement cycle our system already runs against client intake.
First whiteboard. Listened mostly, but the team locked the design-system workstream on his arrival — tiered visual languages for startup / medium / enterprise, plus the production automation layer that reduces dependence on outside agencies.
Building the generative AI visual design system that's currently running on MicroCo / aTwist — consistent character sets, prompt-based visual assets, the production layer Jonny pointed to when he said "Nick and the generative AI… making a consistent character set" is an additional offering we can plug into any client tier. Also starting to piggyback with Jonny on the engine for redundancy.
We agreed on a zero-touch / light-touch / high-touch tier structure, served by a single templatized main product that grows new branches for client-specific needs. The main trunk gets gently optimized; unique features live as separate modules until they're approved into the trunk.
Every report we generate writes back into the graph. We're at roughly 80K nodes; we're targeting 1M by the end of next month. The graph is the IP, and it powers an API subscription that's separate from client subscription revenue.
We can take an enterprise customer tomorrow, with a lot of manual stuff that doesn't scale. June 26 was the date mentioned in the room. The launch sequence has since landed on a two-step: the June 29 weekly stack-rank report goes out first, generated off the 6am Monday daily insight; the two weeks after that are billing and subscription-tier fine-tuning; the full-scale launch is July 13. The first months are high-touch on purpose: we use the first engagements to learn what the automation has to absorb later.
Direct client subscription is one revenue line. The API — the data hose other AI systems pull from — is a second. Licensing SHUR IQ to partner agencies so they can serve their own clients is a third. Each has its own pricing logic.
One brand brain, four offers stacked by client size and growth stage. Each strand has its own intake depth, its own deliverable, and its own pricing intuition.
Startups < $20M revenue · Series A and earlier
Medium $20–100M · New CMO hires · PE-owned brands
$100M+ · PE diligence · M&A · Strategic turnaround
Partner agencies · Embedded in external AI workflows
Nineteen items lifted from the transcript, grouped by owner. Timestamps from the source where stated. Items marked open have no due date the room agreed to.
| # | Item | When |
|---|---|---|
| Jonny | ||
| 01 | Provide updated product offering breakdown and editorial output list to the team for alignment | 01:34:47 |
| 02 | Facilitate integration of Claude session transcripts into client knowledge graphs and product training | 07:49 |
| 03 | Coordinate content and design direction input for AI-generated creative assets and reports | 33:41 |
| 04 | Oversee upcoming visual system and UI improvements with design lead Alex | 01:45:19 |
| Diana | ||
| 05 | Prepare formal intake template drafts and feedback questionnaires for various client tiers | 06:20 |
| 06 | Coordinate transfer and collaboration on Figma whiteboarding sessions for product design | 24:56 |
| 07 | Support client onboarding and manual high-touch delivery for enterprise launch | 01:43:32 |
| 08 | Work with Jonny and Alex on consolidating product visual language and design systems | 01:51:05 |
| Christine | ||
| 09 | Write intake questionnaire for startup process focusing on relevant questions and scoring | 01:57:00 |
| 10 | Provide feedback on product outputs and editorial layout usability from user perspective | 26:48 |
| 11 | Engage in collaborative sessions to refine ideal intake processes and client onboarding | 38:36 |
| Alex | ||
| 12 | Lead design and animation development for AI-generated presentations and client deliverables | 01:46:48 |
| 13 | Integrate AI tools into existing workflows for optimized creative output | 01:48:42 |
| 14 | Develop branded visual systems aligned with client verticals and product tiers | 01:51:05 |
| Nuri | ||
| 15 | Define client segmentation models by lifecycle and growth stage for targeted sales approach | 53:46 |
| 16 | Develop Structural Advantage Score rubric for brand valuation in PE and acquisition contexts | 01:22:04 |
| 17 | Assist in mapping data inputs for industry-specific ontologies and CRM/BI integrations | 01:27:14 |
| Team | ||
| 18 | Plan and execute enterprise MVP launch in two steps: June 29 weekly stack-rank report drop (off the 6am Monday insight), then two weeks of billing and subscription-tier fine-tuning, culminating in the July 13 full-scale launch; high-touch manual delivery throughout | 01:43:32 |
| 19 | Build out API offerings and subscription data feeds to support broader licensing and integration | 36:19 |
This is the cycle our system already runs against every client engagement. SHUR IQ learned it by watching the Shur agency do client work; it now drives intake, synthesis, and the post-call updates that feed the graph.
The intake call. Captures stated problem, growth stage, decision-makers in the room. Different depth per tier — questionnaire for zero-touch, full call for high-touch.
Public filings, social, community forums, App Store reviews, peer IR. For high-touch, add client-supplied documents and CRM integrations (HubSpot, Salesforce).
Brand Power Score / Structural Advantage Score generated. Knowledge graph identifies what's missing, what's plateaued, what competitors hold that this brand doesn't.
Recommendations are built as moves — "doing X should move you up 10 points; Y, five more." Every claim traces to source so the client can challenge it.
Magazine-style layouts — playful for startups, formal for enterprise. Outputs include the report, the viz hub, copyable prompts for downstream tools.
After every client call the system extracts intent, action items, and sentiment. Updates the client's graph and the master graph. The next briefing starts sharper.
The knowledge graph is the durable thing we build. Every client engagement, every transcript, every report we generate becomes a queryable structure that the next engagement reasons over. The graph is what makes our outputs explainable — the client can ask any claim, "where did this come from," and we can show the source statement that produced it.
That's the structural difference from a black-box model: every output traces back to an evidence path. Clients can disagree with us in a specific place, and we update the brain there. It's also the reason the API is a real revenue line on its own — the data hose is worth subscribing to even for someone who never buys a client engagement.
The 1M-node milestone matters because that's the density where the brain stops being a clever assistant and starts being something that holds a consistent point of view across thousands of brands over time. Limore framed the long horizon: keep refining the engine until people return to it for decades.
"Our job is to continue to refine the point of view, the negative space… how much sharper can we make this brain. We started with something that was a blessing and a curse. We've turned it into a really powerful tool."— Limore Shur · 01:38:01
The session locked the spine. It did not close every question. These are the open ones we carry into next week.
The session didn't formally vote on it, but the working consensus is that Reffer functions inside the pitch deck product (Strand 01) as the validating use case. Christine writes the intake template that the next 50 startups will use; the JV gives us our first revenue inside a tier we can otherwise only describe. Reffer doesn't sit beside the four strands — it proves Strand 01 works.
The harder question Christine raised pushes past the JV: what happens when the API matures into something that lives inside Claude, ChatGPT, and Lovable? That's a different go-to-market entirely — closer to platform partnership than client services. We did not close on this. It belongs in the next session.
Six concrete moves that keep the June 29 stack-rank drop and July 13 full launch on rails and move the open questions to closure.
We pulled the whiteboard into a knowledge graph: 77 entities, 16 clusters, modularity 0.72. Then we ran the same negative-space pass we run for clients — on this conversation about how we serve clients. The strongest unspoken move emerged across both latent-topic and conceptual-bridge analysis. Three structural gaps to bridge before we ship.
Christine's intake questionnaire and Diana's onboarding flow are being designed as data-collection mechanisms. The graph suggests they're already brand expressions. Every founder's answer seeds a node. Every relationship between answers is an edge. The questionnaire is not a tool that precedes the brand evaluation — it IS the first brand evaluation, performed live, while the founder is still typing.
Every brand evaluation tool on the market measures a brand as an external artifact — logos, scores, awareness metrics. The graph reframes the product: SHUR IQ's knowledge graph accumulates identity over time through sessions, transcripts, and consensus scoring. We aren't selling brand evaluation. We are selling ontological continuity as a brand service. The brand IS the living memory of how its concepts connect, drift, or fragment over time.
Why it mattersAlex's visual system work and Christine's questionnaire feedback loop are being built in parallel with the startup pitch deck product, but the two haven't been connected. Founders will hit a stitched-together onboarding.
What to buildA single intake artifact that seeds the graph, generates the visual system tier, and outputs the first pitch-deck draft — all from one questionnaire pass.
Why it mattersThe deterministic, source-traced backend (80K nodes today, 1M target) is invisible to the startup tier. We're selling explainability as a moat but not exposing it where it would close the deal.
What to buildA "show your work" surface inside the startup pitch deck product — hover-to-source citations, click-to-trace every claim, the founder can audit their own deck before showing it to anyone else.
Why it mattersThe design feedback loop is being shaped by client preferences (digestibility, tier-appropriate visual language). The Negative Space theoretical anchor is being shaped by Limore alone. If these decouple, the design system will drift from the theoretical underpinning that makes SHUR IQ academically defensible.
What to buildA working session pairing Limore + Alex + Christine specifically on translating Negative Space into per-tier visual grammar — before the design system locks at any of the three tiers.
These are the three questions the whiteboard didn't ask. The next working session should.
brandcentral pivot, connecting evaluation + brain + ecosystem.knowledge_graphruntime backend pulled into both explainability and design.apirevenue gateway between client tiers and external AI models.evaluationverb that ties brand + tool + private equity buyer + CMO.designfast-becoming a cross-cutting concern as Alex onboards.Graph generated 2026-05-26 from the whiteboard transcript and summary — 77 entities, 16 clusters, modularity 0.72. Full graph at infranodus.com/sensecollective/shuriq-whiteboard-2026-05-21/edit. Analyses run: develop_latent_topics, develop_conceptual_bridges, generate_research_questions (with useSeveralGaps), all on claude-sonnet-4.6.