Chat Prompts

I’m creating a knowledgebase for software-as-a-service founders and leaders.

Responses should be in UK english.

I’m making a glossary of useful terms for employees at SaaS companies to understand.

For each of the terms below, write me a concise and clear definition.

Minimum Viable Product (MVP) User Stories Use Cases Product Requirements Document (PRD) Functional Specifications Wireframes Prototypes

Give me your response in JSON following this example:

[{
	'term': 'Annualised Run Rate (ARR)',
	'definition': 'YOUR DEFINITION HERE',
	'key facts': ['fact 1', 'fact 2', 'fact 3', 'fact 4'],
	'quote': {
		quote: 'quote 1',
		citation: 'citation',
		citation_location: 'https://...'
	},
	'tags': ['array', 'of', 'tags'],
	'further reading': [{
		article: 'title of the article',
		location: 'https://...'
	},{
		article: 'title of the article',
		location: 'https://...'
	},{
		article: 'title of the article',
		location: 'https://...'
	}]
}]

Related links should include links to some further reading.

I’m creating a knowledgebase for software-as-a-service founders and leaders.

Responses should be in UK english.

I’m making a glossary of useful terms for employees at SaaS companies to understand.

For each of the terms below, write me a concise and clear definition. For each of the terms below, write me three interesting facts. For each of the terms below, find me three explanatory quotes with correct citations. For each of the terms below, find me three articles where readers can learn more.

Terms

Minimum Viable Product (MVP) User Stories Use Cases Product Requirements Document (PRD) Functional Specifications Wireframes Prototypes

I’m creating a knowledgebase for software-as-a-service founders and leaders.

Responses should be in UK english.

I’m making a glossary of useful terms for employees at SaaS companies to understand.

Make me a list of terms I should include in my glossary under the heading “” Don’t define the terms for me, just give me the list.

Headings

• SaaS business metrics
• Technical terms for non-technical founders
• Product management terms
• Product strategy terms
• Business strategy terms
• Business operations terms
• Customer success terms
• People operations terms
• Software sales terms

I’m creating a knowledgebase for software-as-a-service founders and leaders.

Responses should be in UK english.

A role playbook is like a job or position description, but it is standardised across a business so everyone in a given position shares the same playbook. The idea is for anyone in the business to be able to understand the responsibilities and goals of each person.

Every role playbook consists of:

• A simple explanation of the role
• A list of qualitative goals for the role. Qualitative goals should never be open ended (like “improve customer satisfaction”) but rather describe the desired end state (like “Customers are satisfied with our products and services”)
• A list of responsibilities for the role

Here is an example role playbook for a Product Manager:

Product managers wear many hats. First and foremost, you are a member of a cross-functional product development team—a team which you will work to support in a number of ways with your experience with business and technology.

Qualitative goals

• Their team is rallied behind a unified vision and each member thoroughly understands the impact this vision has on the team, the business, customers and the wider industry.
• Outcomes are prioritised over outputs and scope is lean enough to deliver value without unnecessary effort.
• The product(s) they represent have clearly-defined value propositions which are thoroughly understood by each member of their team as well as all internal and external stakeholders.
• Initiatives are properly scrutinised and considered before they commence and the appropriate documentation (e.g., an initiative brief) has been completed.
• Customer engagement (e.g., customer interviews, site visits) within their team is frequent and productive. Customer needs are considered and form the basis of decision making within the team.
• Upcoming work and progress on work is shared frequently and clearly with the wider organisation, particularly key stakeholders.
• Data is intelligently and transparently consulted to aid decision making wherever possible.
• Features and products are released with minimal friction.
• The business (e.g., sales, marketing, customer support) has an understanding of their product and its features and is capable to support and sell it.

Responsibilities

• Build, measure & learn to make complex easy.
• Help your team to define outcome-centric initiatives, user stories and tasks, aligned to the vision, values and measures to which your team is aligned.
• Define success and failure measures, and ensure every completed task and initiative is measured and assessed by this criteria.
• Document and regularly share learnings with your team and the wider business.
• Demonstrate and reflect on value delivered, or undelivered.
• Encourage your team to embrace complexity and remove uncertainty through experimentation.
• Encourage a culture of learning and sharing. Every initiative or task is an experiment to be validated.
• Bring value to market
• Ensure the wider business understands how your product works, who it’s intended for and the benefits it delivers. Personally involve yourself in efforts to demonstrate and expose what you are building.
• Provide marketing and sales with the information they require to execute launch campaigns and ongoing marketing/sales efforts.
• Test solutions with customers and prospects.
• Measure the outcomes of what is being built.
• Practice radical transparency with your colleagues, especially when it comes to data and other information you may have special access to.
• Be frugal and pragmatic. Cutting scope is a good thing, we’re looking for outcomes, not lines of code.
• Communication and visualisation
• Clearly and regularly communicating development milestones, key decisions and customer insights, to stakeholders.
• Experimenting with and finding effective ways to visualise and disseminate information.
• Keep your team in the loop. We work hard to give our teams as much autonomy as possible, but sometimes priorities will change for reasons outside of their control. You need to ensure they don’t feel caught off guard.
• You are the face of your product(s) and will be required to regularly represent your product(s) to various audiences including your team, the wider business, partners, customers, prospects and industry peers.
• Customer intimacy
• Engage with those who speak more regularly with customers (e.g., customer success, support, sales).
• Cut out the middleman. Go see your customers in person and contact them over the phone.
• Find quantitative ways to engage. Interviews and surveys are great, but also consider how you can analyse the data we have (e.g., support tickets, ideas, phone calls, bug submissions) to understand the market.
• Represent the business and the user, but don’t monopolise your insights. Don’t just represent the needs of external parties—expose your team to these parties. Your team should be able to prioritise work without you

Write me a role playbook, in markdown, for a Customer Success Manager

I’m creating a knowledgebase for software-as-a-service founders and leaders.

Responses should be in UK english.

I’m writing an advice column for founders of SaaS companies.

Imagine you are a founder of an early stage B2B SaaS startup who wants advice.

Give me a list of very concise questions that you would ask me. Give me five for each topic below:

• Finding product-market fit.
• Scaling operations as your startup grows.
• Establishing new functions within the business.
• Product strategy.