From your first idea to daily operations, plan your next step as a solo founder.

Help us conduct subscription churn analysis according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Check the definition, period, customer group, and reason for churn, and do not overinterpret small samples. [Results to be created this time] Read the provided draft and select the omissions, contradictions, and lack of evidence that prevent you from achieving your goal in order of greatest impact. Please include the original text location, problem, impact on readers, and minimum revisions. Don't treat simple differences in taste as errors, but be sure to identify what needs to be fixed before rewriting the entire thing. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that each problem you point out has textual support and that the amendments do not change the original meaning. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us work on the experiential customer operation plan according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Distinguish between participation conditions, scope of support, actions to be observed, and judgment after completion. [Results to be created this time] Compare the data with previous feedback, organize changes to be reflected, and write a revised version. For conflicting feedback, explain the options based on purpose and reader criteria. Briefly compare what was kept, what was changed, and the reason for the change, and do not add new facts. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure previously confirmed conditions are preserved and requested feedback is reflected. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us align our competitive alternative mapping efforts with the goals and resources below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Compare direct competition, indirect alternatives, and manual efforts with the same customer goal. [Results to be created this time] Compare the initial goal and actual results and share good choices, stuck points, and lack of evidence. Instead of criticizing the judgment at the time based solely on the results, choose no more than two hypotheses to change. Please suggest indicators to maintain, change, and observe in the next attempt. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure you have concrete data to compare improvements to in the next attempt. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

You are a hands-on designer who supports a one-person team in product planning and execution. Write down the “4-Week MVP Scope Determination” as a specification that can be used in actual work. [Key tasks] Prioritize the required and excluded features and success metrics to launch {{product}} within 4 weeks. [Additional input] User/Current Stage/Goal: {{business_context}} Verifiable evidence: {{evidence}} Resource, Operational and Technology Constraints: {{constraints}} [Working Procedure] Select the one riskiest business assumption. Functions are divided into essential, manual replacement, and post-launch, leaving only the core flow that verifies them. Set a four-week schedule and buffer based on available time. First find the biggest uncertainty and the minimum work to verify it. Instead of an idealistic design that ignores resources and dependencies, distinguish between what's feasible now and what can be expanded later. If you have alternatives, compare at least two on the same basis. [Output contract] Assumptions/Success Criteria → Scope Comparison Table → 4-Week Plan → Dependencies → Release Blocking/Reduction Criteria Don't just describe the document template, fill it with actual content tailored to the services provided. If necessary, provide a pair of real example inputs and expected results, but specify that these are hypothetical examples. [Quality standards] Do not include all requests as required or omit operation/inspection times. If you're missing information that's essential to your decision, ask up to three questions first. Separate remaining unconfirmed items into [Confirmation required] and design assumptions into [Assumptions]. Do not mix confirmed facts, suggestions, and unverified items. Rather than creating cost and performance figures, write down the formulas and required inputs. Do not include sensitive information and actual secret values ​​in the document. At the end, leave an order of execution and a way to confirm completion of each step.

Help us compare sales channels based on the goals and data below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Compare customer suitability, fees, operating hours, and conditions for maintaining customer relationships. [Results to be created this time] Distinguish between information that can be confirmed based on current data and information gaps that change the outcome. Write down the reasons for each question and the parts that vary depending on the answer, and suggest up to three questions to check first. Once you receive the answer, please update the agreed upon task summary. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Please check whether the question already has an answer in existing materials or is simply a question of preference. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us align our competitive alternative mapping efforts with the goals and resources below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Compare direct competition, indirect alternatives, and manual efforts with the same customer goal. [Results to be created this time] Create a handover document focusing on the current status, what has already been decided, open questions, next actions, and data location. For the person in charge and the deadline, only write what is provided and leave the undecided ones as is. Leave the necessary context so that people who haven't read the original can take the first step. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure recipients know what to look for, where to look, and what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us work on the business indicator dashboard according to the goals and data below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Define calculation formula, source, cycle, responsibility, and action in case of abnormality for each indicator. [Results to be created this time] In this material, create an empty form to separate the structure to be reused from the content that changes every time. Briefly describe the content and standards for writing in each space, and provide an example filled with current data. Don't include one-off proper nouns or fictitious achievements as fixed rules. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] You can use the same form for other cases and make sure that required inputs are not omitted. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Please help me work on the recommendation request method according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] We consider the time of confirmation of satisfaction and the burden of the request, and do not hide false reviews or compensation. [Results to be created this time] Compare the initial goal and actual results and share good choices, stuck points, and lack of evidence. Instead of criticizing the judgment at the time based solely on the results, choose no more than two hypotheses to change. Please suggest indicators to maintain, change, and observe in the next attempt. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure you have concrete data to compare improvements to in the next attempt. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us work on the market size assumption table according to the goals and data below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Reveals calculation formula, source, scope, and possibility of duplication and does not fill in unconfirmed numbers. [Results to be created this time] Figure out the purpose and audience first, and then write the actual draft starting from the parts that contain the necessary information. Change the flow of background, key points, evidence, and next actions to fit the topic, and mark parts with missing data as requiring confirmation. The results are divided into a draft that can be edited immediately and a remaining verification question. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure all the facts and figures in your draft match the input and allow the reader to know what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us work on customer problem hypotheses according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Inconvenience, current alternative, frequency of occurrence, and willingness to pay are divided into observation and hypothesis. [Results to be created this time] Compare the data with previous feedback, organize changes to be reflected, and write a revised version. For conflicting feedback, explain the options based on purpose and reader criteria. Briefly compare what was kept, what was changed, and the reason for the change, and do not add new facts. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure previously confirmed conditions are preserved and requested feedback is reflected. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us work on the prototype evaluation criteria according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Establish success criteria based on customer behavior and distinguish between favorable responses and actual usage. [Results to be created this time] In this material, create an empty form to separate the structure to be reused from the content that changes every time. Briefly describe the content and standards for writing in each space, and provide an example filled with current data. Don't include one-off proper nouns or fictitious achievements as fixed rules. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] You can use the same form for other cases and make sure that required inputs are not omitted. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us conduct subscription churn analysis according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Check the definition, period, customer group, and reason for churn, and do not overinterpret small samples. [Results to be created this time] Figure out the purpose and audience first, and then write the actual draft starting from the parts that contain the necessary information. Change the flow of background, key points, evidence, and next actions to fit the topic, and mark parts with missing data as requiring confirmation. The results are divided into a draft that can be edited immediately and a remaining verification question. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure all the facts and figures in your draft match the input and allow the reader to know what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us configure the rate plan according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Differences in usage and functionality by customer group are linked to billing units. [Results to be created this time] Compare the data with previous feedback, organize changes to be reflected, and write a revised version. For conflicting feedback, explain the options based on purpose and reader criteria. Briefly compare what was kept, what was changed, and the reason for the change, and do not add new facts. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure previously confirmed conditions are preserved and requested feedback is reflected. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us review discount conditions according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] We look at short-term sales, contribution margin, impact on existing customers, and termination conditions together. [Results to be created this time] If there are alternatives provided, compare them based on the same criteria. If not, suggest two possible approaches based on the current data. Distinguish between appropriate situations, pros and cons, required data, and what to give up for each approach. Rather than saying that one is unconditionally better, please write down the basis for your choice based on the input conditions. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that the comparison criteria and assumptions are applied equally to all alternatives. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.