Use Claude to explore a direction, test assumptions and choose a bounded next step. Start with your experience and constraints when the idea is unclear, or current product evidence when you have it. Save reviewed findings so later scope and marketing work can use what you learned.

This guide is for a technical solo founder running a small software product. It explains the operating method; the separate Claude connection guide covers remote MCP setup and a connection test. Examples below are fictional, not customer results.

Choose a home for your product context

Your assistant needs to know who the product serves, what exists today, what customers have actually said and which choices you accepted. A polished answer can otherwise optimize for an imagined audience or a feature that has not shipped.

Claude Projects let you supply knowledge and reusable project instructions. Use those to maintain a compact working context when that fits your workflow. See Claude's project instructions guide.

A product workspace serves a different need: the current product records need to remain accessible across repeated tasks and compatible AI clients. 1PC stores founder constraints, versioned knowledge, accepted decisions and structured progress. Claude can access those records through an authorized MCP connection. Compare Markdown context files with an MCP workspace before choosing more infrastructure.

Already running a product? Use the existing-product intake guide to collect its current offer and sourced context. An existing product does not need to start again with an idea exercise.

Match Claude to the decision in front of you

Choose the question before choosing the tool. A customer problem, a feature decision and a launch message need related facts but different evidence. The table gives a small set of useful starting points; each linked guide owns the full method.

Your situationUseful requestWhat to review
You have no clear idea yet.Compare directions from my experience, constraints and the people I can reach.Founder context: feasibility, unknowns and the next question to investigate.
You have an untested idea.Separate the problem hypothesis from evidence and propose a reachable validation experiment.Validation: actual observations, sample limits and what would change the choice.
You have several competing tasks.Read accepted decisions and open work; recommend one priority within this week's capacity.Weekly product review: dependencies, constraints and the cost of delaying other work.
You accepted a feature scope.Connect the supported benefit to one launch message and a small channel experiment.Feature launch marketing: released versus planned claims, audience and measurement.
You repeat the same review method.Use my published private checklist with this product's current inputs.Custom product skills: declared inputs, result destination and completion criteria.

Claude's available browsing, coding and other tools depend on the surface you use and its permissions. Loading a 1PC skill supplies guidance and requirements; it does not add a browser, repository checkout or publishing integration to the host.

Enter Product Owner before each task

A remote MCP connector makes 1PC tools available. It does not automatically install the native Product Owner skill packaged with the ChatGPT plugin. Set an explicit operating instruction in your Claude project or supply it when beginning the task; the setup guide includes a copyable bootstrap.

The intended entry is practical: read the founder workspace, select the right accessible product, load Product Owner requirements and summarize the saved state. Discover the skill catalog, then load only the guidance relevant to the requested work. If a landing page already exists or a change affects an accepted feature choice, explain that before rerunning the work and resolve any unclear scope.

A state question stays read-only. SEO, outreach and other suggestions remain proposals until you authorize work. Every 1PC User has the available skill catalog and private workspace skills; private MCP calls consume prepaid credit. See current pricing.

A small operating loop for a working SaaS

Imagine Follow-up Board, a fictional SaaS for freelance designers tracking unanswered proposals. Its saved scope includes a manual reminder list. Automatic email sending is only a proposed feature. The founder has four hours available this week and wants to decide how to explain the existing reminder benefit.

Use 1PC Product Owner for Follow-up Board.
Read the current product context, accepted decisions and open work.
First summarize what exists and what remains proposed.

Recommend one next task within my four-hour budget.
If launch messaging is appropriate, suggest a focused deliverable
using only supported product behavior. Explain what source context
you used and what evidence is still missing.
Keep this first response read-only.

Check that the response recognizes the manual reminder list and does not advertise automated sending. If the state is wrong, correct the interpretation or stale record before drafting. If you accept the proposed messaging task, authorize the draft and its save destination. Saving the draft does not publish the landing page.

Finish by verifying what was saved, then open a fresh session and ask for the current choice and next action. Use the cross-client continuity check to compare the answer with the actual record.

Start with one verified connection and one task

Claude documents remote custom MCP connectors; 1PC exposes an authenticated remote MCP server. Those capabilities are the basis for the setup method, not a claim that this article records a completed live Claude connection. Read Claude's connector documentation, then use the 1PC setup and smoke test.

Start with a fictional or low-sensitivity product. Verify the correct account, available tools and selected product before relying on writes. Keep necessary business facts in the workspace and consider both 1PC and the AI host's data handling before supplying customer material.

Once the read/save/resume loop works, use it for a real weekly review or a scoped launch task. Continuity comes from reviewed, saved outcomes and a fresh read of the current state. An unsaved conversation does not become a shared product record.

Connect Claude to your product workspace.

Follow the remote MCP setup guide, then verify a read-only state request before saving your first result.

Set up Claude and 1PC ↗