As covered in
Forbes · TechCrunch · Al Jazeera · HuffPost
02 · The document
What you walk away with
By the end of the 2 hours you have a working document with all of the following, written on the call and ready to forward to your team.
- Use-case clarification, written in a single sentence using the Sprint Brief template.
- Data and API readiness assessment for the candidate workflow.
- Recommended workflow scope (or a recommended deferment, with reasoning).
- A go / no-go memo on whether a Sprint is the right next step.
- A Sprint Brief draft if there's a strong fit, including success criteria and out-of-scope items.
- Honest answers about what fits in 10 business days and what doesn't.
03 · Fit
Who this is for
- B2B SaaS founders or product leaders considering shipping an AI feature.
- Teams that have tried building AI features and gotten stuck somewhere between prototype and production.
- Teams that know AI should be part of their product but want a second opinion before committing engineering time.
- Teams comparing Sprint vendors and wanting to validate fit before signing.
Who this is not for
- Teams looking for a generic AI strategy consultation.
- Solo indie hackers without a B2B SaaS product.
- Enterprise teams with formal procurement or RFP processes.
- Anyone who wants a quick first conversation. Start with the free 15-minute Scoping Call.
04 · The two hours
How a Discovery Day works
The 2 hours are structured but not rigid. Rough shape:
Minutes 0–30: Your context. Current product, team, AI experiments to date, what's worked and what hasn't, what's pulling the AI conversation forward inside your company.
Minutes 30–75: The candidate workflow. Inputs, outputs, users, data sources, current manual process, what good output looks like, who reviews it before it ships.
Minutes 75–105: Feasibility. What fits in a 10-day Sprint and what doesn't. Risk classification (low / medium / high). Integration complexity. Where the Day-5 prototype likely lands.
Minutes 105–120: The memo. Go / no-go recommendation, Sprint Brief draft (if applicable), scoping language, next-step recommendation. Shared as a Google Doc you keep.
About half of Discovery Days end with a Sprint recommendation. The other half end with "here's what to do first, come back when X is in place." Both are valid outcomes. The point of a Discovery Day is to find out which one you are, not to convince you to buy a Sprint.
05 · The credit
The credit toward Sprint
If you continue to a full Sprint within 14 days of your Discovery Day, the $500 is credited against the Sprint price.
So a Discovery Day followed by a Sprint costs the Sprint price, not the Sprint price plus $500.
If we agree the Sprint isn't the right next step, the $500 covers the working document and the 2 hours. No upsell, no follow-up sequence, no retainer pitch.
06 · Before the call
What I need from you before the call
A short pre-call form, sent after booking. Three things:
- The workflow you're considering. One paragraph is enough. Examples I've worked through with other founders: investor update assistant, runway scenario explainer, customer summary generator, support ticket triage, onboarding assistant.
- Your stack and data access. What's your product built in, where does the relevant data live (Stripe, your DB, HubSpot, Linear, Notion, your CRM, your admin), and what AI provider you already use (Anthropic, OpenAI, Bedrock, Vertex) if any.
- The decision-maker question. Who needs to approve a Sprint, and are they on the call. If they're not, a Discovery Day is fine, but the Sprint recommendation will be harder to act on.
That's it. No data dumps, no NDAs to sign before the call. We sign a mutual NDA on the call itself if either side wants one.
07 · Who's behind it
Why work with me
I'm Nasser Ghanemzadeh. I've spent 17+ years on the customer side of software, as CEO, CPO, and product lead. I built and exited Nivo (200K+ users, 450% revenue growth, acquired), led product at Pangouan, co-founded Iran Startups, and ran the Finnova accelerator. These days I build Vectig, an AI-native startup finance product, shipped daily with Claude Code and MCP.
Speaking on AI-native product development: OMR Festival, re:publica, GITEX EUROPE.
A Discovery Day points that experience at your roadmap for two hours. Based in Turkey, available across European, Middle Eastern, and North American business hours.
FAQ
What if we decide not to do a Sprint after the Discovery Day?
Then you walk away with the working document, the go / no-go memo, and 2 hours of focused outside-perspective on your AI roadmap. No follow-up sales sequence. You're free to take the memo to another vendor, to your internal team, or to nobody at all.
Do you sign an NDA?
If either side wants a mutual NDA, we sign one on the call itself before getting into specifics. I don't ask for NDAs to be signed before booking, and I don't expect you to.
What if our data isn't ready?
That's one of the most common Discovery Day outcomes: "the workflow makes sense, but the data foundation isn't there yet." The memo will say exactly what to do first, usually a 2 to 4 week data-readiness project that you can run internally, and we revisit Sprint readiness when it's done.
How is this different from the free Scoping Call?
The Scoping Call is free and takes 15 minutes: we pick the workflow and check whether your data can carry it in ten days. The Discovery Day is a paid two-hour working session that ends with a written document you keep: the scope, a go/no-go memo, and a Sprint Brief draft if there is a fit. Most founders start with the call.
What if I'm not sure I want a Sprint yet?
Then a Discovery Day is exactly the right starting point. About half of them end with a deferment recommendation. That's a feature, not a failure mode.
Can a co-founder or technical lead join?
Yes. Up to three people from your side on the call. Beyond three the conversation slows down. If you want broader team alignment, the right pattern is: founder + tech lead on the Discovery Day, then I record a Loom walkthrough of the memo for everyone else.
What if our use case is in a high-risk category (legal, medical, compliance, payments)?
The Discovery Day still works, but the Sprint recommendation will likely be "not yet" or "redefine scope to a lower-risk adjacent workflow." High-risk first Sprints don't make sense for teams new to AI deployment. The memo will explain what does.
Do you work with companies outside B2B SaaS?
Mostly no. The methodology, examples, and Sprint structure are built around founder-led B2B SaaS at 5 to 50 people, post-product-market-fit. If you're outside that, the Discovery Day may still be useful but the Sprint may not be the right vehicle.
08 · Book it
Two hours, one document, a clear next step.
Book a Discovery Day for a focused outside read on whether the AI feature you're considering is ready to ship in 10 business days. Or start with the full breakdown of the 10-day FDE Sprint.