What should your product do next?
A 30-minute Product Strategy session with Feature1.
You bring your product and the decision you are working through. We work through your customers, competitors, business goals and current priorities, then review a draft Product Strategy Narrative together. No code access needed.
A paid session, from $59, depending on the complexity of the product. No code access needed. The narrative is a starting point to challenge, not a finished strategy.
Why this exists
AI made building fast. It did not make deciding what to build any faster. In the teams we work with, delivery sped up and the queue moved to the decisions in front of it. One team hired a second product manager for exactly that reason. The session is the first step of working the other way round: direction first, then the build.
What happens in the 30 minutes
Before the call
You send your website, your role, and one product decision you are working through. Public material is welcome. Nothing else is required.
Minutes 0 to 8
Business goal, the customers you actually serve, the people inside them, and the constraints you are working under.
Minutes 8 to 18
We challenge the market and competitor assumptions, and separate what you know from what you are guessing.
Minutes 18 to 25
We review the draft Product Strategy Narrative together, as Feature1 has written it from the conversation.
Minutes 25 to 30
You correct it, accept it or ask for a revision, and we agree the next decision.
What you leave with
- A draft Product Strategy Narrative
- One page, within 24 hours. Where you win, for whom, and the two or three advantages worth compounding. It should contain at least one thing you did not already believe, or it is a summary, not a strategy.
- Three candidate initiatives
- The directions the narrative points at, in plain language, ready to be argued with.
- The next decision
- Named. Not a roadmap, one decision, and what would settle it.
Who it is for
Founders and product leaders with a live product and a decision to make. It works best when the person who decides what gets built is on the call. It is not for an idea without a product yet, and it is not a sales demo.
What comes after, if the direction holds
We know where you want to go. The next step is seeing where you are. You connect your product and Feature1 reads what it can already do, shows the gap between the narrative and the product, and turns the initiatives that close it into features, stories and acceptance criteria your team builds from. That step is optional and comes only after the narrative lands.
Before you book
Is this consulting?
It is the first step of using Feature1. The narrative comes out of the conversation through Feature1, and everything after it, connecting your product, seeing the gap, planning the work, happens in Feature1. You are not buying an hour of advice; you are starting with direction before the build.
Do I need to connect my code or GitHub?
No. The session needs nothing but you, your product and a decision. Connecting the product is a later, optional step, and it happens only after the narrative lands.
Will the strategy be finished in 30 minutes?
No. You leave with a draft narrative and a named next decision. It is written to be challenged. Finalising it is your call, and a second pass is a normal outcome.
What if the direction does not hold?
Then the session did its job early. A narrative that turns out to be wrong in 30 minutes is cheaper than a quarter of building toward it.
Who runs it?
Abdulrahman, founder of Feature1, with Feature1 doing the research and writing during the call. Sessions are limited each week so every narrative gets the follow-up it needs.
Do you record the call?
Only with your permission. Reviewed notes are enough for the narrative.
Bring the decision you are stuck on.
Thirty minutes to establish direction. The rest follows from it.