# Document examples, not templates > Clarity, documented. Start with a problem. Ainna frames it with you, brainstorms the ideas, grades them against the evidence and works the strongest through: who it's for, the market, the competition, the product and the plan. Then it packages the work as any of these documents, from a problem framing deck to a pitch, a PRD or the system's architecture. Page: https://ainna.ai/documents · Updated 6 October 2026 · Document designs by George Krasadakis These are not templates; they are the deliverables. A template gives you headings to fill. Each document below is the work, distilled: Ainna works through the problem and the idea with you, runs the analyses (the personas, the market sizing, the competition, the product definition, the system model) and packages the result as a finished PowerPoint deck or Word document, designed to be presented. The twelve are written from the same work, so they agree with one another. ## The problem ### [Problem Framing Document](https://ainna.ai/documents/problem-framing-document) Word, 5 pages. A problem framing document defines a challenge before anyone proposes a solution: who it affects, what it costs, the evidence, why now, and what solved would look like. - Inside: in short; current and ideal state; how people cope today; why now; what solved looks like; open questions; the evidence, reported or assumed; the grade; the board, and what people said. - Distilled from: the framing session, the evidence logged with its sources, the brainstorm board and what people said. - On show: page 1, title page (https://ainna.ai/images/examples/problem-framing-document-example-01-1200.webp); page 2, part one, the problem (https://ainna.ai/images/examples/problem-framing-document-example-02-1200.webp); page 3, what it rests on (https://ainna.ai/images/examples/problem-framing-document-example-03-1200.webp). The other 2 pages stay closed. - Its page: https://ainna.ai/documents/problem-framing-document · Markdown: https://ainna.ai/documents/problem-framing-document.md - Guide: [What Documents Do You Need for Product Discovery?](https://ainna.ai/resources/faq/product-discovery-documentation-faq) ### [Problem Framing Deck](https://ainna.ai/documents/problem-framing-deck) PowerPoint, 11 slides. A problem framing deck presents a problem as slides: what goes wrong and for whom, the evidence, why now, what solved would look like and how it grades, so a team agrees on the problem before anyone pitches a solution. - Inside: taken apart; the evidence, in figures; where things stand; why now; who it touches; what solved looks like; how it grades; the questions it raises; directions on the board. - Distilled from: the framing, its evidence and grade, and the ideas on the board. - On show: slide 1, cover (https://ainna.ai/images/examples/problem-framing-deck-example-01-1200.webp); slide 3, the evidence (https://ainna.ai/images/examples/problem-framing-deck-example-03-1200.webp); slide 10, directions on the board (https://ainna.ai/images/examples/problem-framing-deck-example-10-1200.webp). The other 8 slides stay closed. - Its page: https://ainna.ai/documents/problem-framing-deck · Markdown: https://ainna.ai/documents/problem-framing-deck.md ### [Problem Social Carousel](https://ainna.ai/documents/problem-carousel) PowerPoint, 5 portrait slides. A problem social carousel tells a problem in five portrait slides for LinkedIn or Instagram: who it hurts, the evidence and what good looks like, ending on a question for your network. - Inside: a cover that stops the scroll; taken apart; why it matters; what good looks like; a question for your network. - Distilled from: the framing and its strongest evidence. - On show: slide 1, cover (https://ainna.ai/images/examples/problem-carousel-example-01-1200.webp); slide 3, why it matters (https://ainna.ai/images/examples/problem-carousel-example-03-1200.webp). The other 3 slides stay closed. - Its page: https://ainna.ai/documents/problem-carousel · Markdown: https://ainna.ai/documents/problem-carousel.md ### [Brainstorm Outcomes Deck](https://ainna.ai/documents/brainstorm-deck) PowerPoint, 10 slides. A brainstorm outcomes deck reports what a brainstorm produced to the people who weren't in the room: the problem, a slide for each promoted idea, what's still open, what was ruled out and why, and how the session ran. - Inside: the question; the stakes, in numbers; what solved looks like; the ideas promoted; the ideas still open; the ideas ruled out, with reasons; how the session ran. - Distilled from: the brainstorm board: every idea, where it stands, the Judge's grade, and the reason behind each decision. - On show: slide 1, cover (https://ainna.ai/images/examples/brainstorm-deck-example-01-1200.webp); slide 5, the outcome (https://ainna.ai/images/examples/brainstorm-deck-example-05-1200.webp); slide 6, idea 01 (https://ainna.ai/images/examples/brainstorm-deck-example-06-1200.webp). The other 7 slides stay closed. - Its page: https://ainna.ai/documents/brainstorm-deck · Markdown: https://ainna.ai/documents/brainstorm-deck.md - Guide: [How Does AI Transform Brainstorming and Ideation?](https://ainna.ai/resources/faq/ai-brainstorming-ideation-faq) ## The idea ### [Idea One-Pager](https://ainna.ai/documents/idea-one-pager) Word, one page. An idea one-pager distils a concept to a single page: what it fixes, how it works, and the essentials at a glance, ready to share. - Inside: what it fixes; how it works; at a glance: users, market, business model and form factor. - Distilled from: the idea's definition: what it fixes, how it works, the users, the market and the business model. - On show: page 1, the one page (https://ainna.ai/images/examples/idea-one-pager-example-01-1200.webp). The other 0 pages stay closed. - Its page: https://ainna.ai/documents/idea-one-pager · Markdown: https://ainna.ai/documents/idea-one-pager.md - Guide: [What Is a Product One-Pager, and How Do You Write One?](https://ainna.ai/resources/faq/one-pager-guide-faq) ### [Idea Social Carousel](https://ainna.ai/documents/idea-carousel) PowerPoint, 5 portrait slides. An idea social carousel tells an idea in five portrait slides: a bold cover, the pain, the idea in three steps, what changes, and a call to action. - Inside: a cover that stops the scroll; the pain; the idea, in three steps; what changes; a call to action. - Distilled from: the idea's definition, the need behind it and its success measures. - On show: slide 1, cover (https://ainna.ai/images/examples/idea-carousel-example-01-1200.webp); slide 3, the idea (https://ainna.ai/images/examples/idea-carousel-example-03-1200.webp). The other 3 slides stay closed. - Its page: https://ainna.ai/documents/idea-carousel · Markdown: https://ainna.ai/documents/idea-carousel.md - Guide: [How Do You Validate a Startup Idea Before Building?](https://ainna.ai/resources/faq/startup-idea-validation-faq) ### [Pitch Deck](https://ainna.ai/documents/pitch-deck) PowerPoint, 16 slides. A pitch deck makes the case for a concept, slide by slide: the problem, the users, the market, the competition, the product, the business model and the ask. - Inside: the problem; why now; the solution; who it's for; why it wins; the market; the landscape; business model; go-to-market; how we'll know; the plan; the team; the ask; the vision. - Distilled from: six analyses: the personas, the market sizing, the competitive map, the product definition, the business plan and the delivery plan. - On show: slide 1, cover (https://ainna.ai/images/examples/pitch-deck-example-01-1200.webp); slide 4, the solution (https://ainna.ai/images/examples/pitch-deck-example-04-1200.webp); slide 12, the plan (https://ainna.ai/images/examples/pitch-deck-example-12-1200.webp). The other 13 slides stay closed. - Its page: https://ainna.ai/documents/pitch-deck · Markdown: https://ainna.ai/documents/pitch-deck.md - Guide: [How Do You Create a Pitch Deck That Wins Investor Meetings?](https://ainna.ai/resources/faq/pitch-deck-guide-faq) ## The product ### [Product Requirements Document (PRD)](https://ainna.ai/documents/prd) Word, 20 pages. A product requirements document (PRD) says what to build and why: the users, the requirements as user stories, the MVP scope, success metrics, risks and the delivery plan, clear enough for engineers and for leadership. - Inside: the product at a glance; the need; the users, in full; the solution and the happy path; the MVP, and what is out; requirements, as user stories; quality requirements; business model; risks; plan and success metrics. - Distilled from: six analyses: the personas, the market sizing, the competitive map, the product definition, the business plan and the delivery plan. - On show: page 1, title page (https://ainna.ai/images/examples/prd-example-01-1200.webp); page 7, the solution and the happy path (https://ainna.ai/images/examples/prd-example-07-1200.webp); page 9, requirements (https://ainna.ai/images/examples/prd-example-09-1200.webp). The other 17 pages stay closed. - Its page: https://ainna.ai/documents/prd · Markdown: https://ainna.ai/documents/prd.md - Guides: [How Do You Write a Great PRD?](https://ainna.ai/resources/faq/prd-guide-faq) · [How Do You Write User Stories That Actually Drive Development?](https://ainna.ai/resources/faq/user-stories-agile-faq) ### [Product Requirements Deck](https://ainna.ai/documents/prd-deck) PowerPoint, 42 slides in four parts. A product requirements deck presents the PRD for alignment meetings, in four parts (discover, define, build and launch), with the requirements in an appendix. - Inside: executive summary; discover: the need, the users, the market, the competition; define: vision, value, the happy path, the MVP, the business model; build: hypotheses, risks, experiments, technology, the team; launch: go-to-market, growth, the ask; appendix: requirements and sources. - Distilled from: the same six analyses as the PRD, set as slides. - On show: slide 1, cover (https://ainna.ai/images/examples/prd-deck-example-01-1200.webp); slide 17, the happy path (https://ainna.ai/images/examples/prd-deck-example-17-1200.webp); slide 26, risks (https://ainna.ai/images/examples/prd-deck-example-26-1200.webp). The other 39 slides stay closed. - Its page: https://ainna.ai/documents/prd-deck · Markdown: https://ainna.ai/documents/prd-deck.md - Guide: [What is a Visual PRD?](https://ainna.ai/resources/faq/visual-prd) ### [PRD Executive Brief](https://ainna.ai/documents/prd-brief) PowerPoint, 14 slides. A PRD executive brief puts the PRD's case on a dozen slides for the meeting that decides: need, users, market, edge, MVP, pricing, plan, risks, metrics and the ask. - Inside: executive summary; the need; the users; market size; differentiation; value proposition; the MVP; revenue model; implementation; risks; product performance; the ask. - Distilled from: the same six analyses, cut to what a decision needs. - On show: slide 1, cover (https://ainna.ai/images/examples/prd-brief-example-01-1200.webp); slide 2, executive summary (https://ainna.ai/images/examples/prd-brief-example-02-1200.webp); slide 11, risks (https://ainna.ai/images/examples/prd-brief-example-11-1200.webp). The other 11 slides stay closed. - Its page: https://ainna.ai/documents/prd-brief · Markdown: https://ainna.ai/documents/prd-brief.md - Guide: [How Do You Write a Great PRD?](https://ainna.ai/resources/faq/prd-guide-faq) ## The build ### [Functional Requirements Specification (FRS)](https://ainna.ai/documents/frs) Word, 13 pages. A functional requirements specification (FRS) defines, testably, how a system must behave: business rules, validations, exceptions, interfaces and acceptance tests, each traced to the PRD. Also called a functional specification (FS or FSD); close to what ISO/IEC/IEEE 29148 calls a software requirements specification (SRS). For software, digital and integration concepts. - Inside: purpose, audience and scope; actors, roles and permissions; rules that hold across the system; compliance touchpoints; each functional area, requirement by requirement; business rules and validations; inputs, outputs and data handling; exceptions and system responses; interface behaviour; acceptance and test conditions; traceability to the PRD; assumptions and glossary. - Distilled from: the PRD's requirements, a check of the concept's scope, and a system model of its actors, capabilities, components, interfaces and data. - On show: page 1, title page (https://ainna.ai/images/examples/frs-example-01-1200.webp); page 4, rules, compliance, then the first area (https://ainna.ai/images/examples/frs-example-04-1200.webp); page 12, traceability (https://ainna.ai/images/examples/frs-example-12-1200.webp). The other 10 pages stay closed. - Its page: https://ainna.ai/documents/frs · Markdown: https://ainna.ai/documents/frs.md ### [System Analysis, Design and Architecture](https://ainna.ai/documents/architecture) Word, 9 pages, with diagrams. A system analysis, design and architecture document describes a system at a high level: its context and logical architecture as diagrams, its components, integrations, data, security, deployment and the key decisions. For software, digital and integration concepts. - Inside: the architecture in brief; what drives it; the system in context, as a diagram; the logical architecture, as a diagram; components and their responsibilities; integration patterns; data and its stores; quality attributes, with targets; security; deployment and recovery objectives; architecture decisions; risks and transition. - Distilled from: the PRD, and the same system model as the FRS. - On show: page 1, title page (https://ainna.ai/images/examples/architecture-example-01-1200.webp); page 3, the system in context (https://ainna.ai/images/examples/architecture-example-03-1200.webp); page 4, logical architecture (https://ainna.ai/images/examples/architecture-example-04-1200.webp). The other 6 pages stay closed. - Its page: https://ainna.ai/documents/architecture · Markdown: https://ainna.ai/documents/architecture.md ## Clarity, by design Every document is architected and designed for one purpose: clarity. The designs are original, built on the method of Innovation Mode 2.0 (Springer Nature, 2026), where some of them are published. Its author, George Krasadakis, has spent 25 years building products, in a career that spans Microsoft, Accenture, GSK and ResMed. Ainna distils your work into each one: every claim in its place, every figure with its source or its assumption. Decks are set in Roboto, documents in Georgia. ## Questions **Are these templates?** No! These are the deliverables! A template gives you headings to fill; these are the finished documents that come out of the work. Ainna works through the problem and the idea with you, runs the analyses (the personas, the market sizing, the competition, the product definition, the system model) and packages the result as a finished PowerPoint deck or Word document, designed to be presented. **What documents can Ainna write?** Twelve, in four stages. For the problem: a problem framing document, a problem framing deck, a problem social carousel and a brainstorm outcomes deck. For the idea: an idea one-pager, an idea social carousel and a pitch deck. For the product: a product requirements document (PRD), a product requirements deck and a PRD executive brief. For the build: a functional requirements specification (FRS) and a system analysis, design and architecture document. Which ones you can create depends on your plan. **What is the difference between a PRD and an FRS?** A PRD says what to build and why: the problem, the users, the requirements as user stories, the scope and the plan. An FRS says exactly how the system must behave: every rule, validation, exception, interface and acceptance test, traced back to the PRD's requirements. Product and leadership decide with the PRD; engineers and testers build and test from the FRS. **Is an FRS the same as an SRS?** Close, and many teams use the names interchangeably. ISO/IEC/IEEE 29148, the international standard for requirements engineering, calls the software-level document a software requirements specification (SRS) and gives it all of a system's requirements, functional and non-functional. An FRS, also called a functional specification (FS or FSD), concentrates on the functional side: how the system must behave, rule by rule, with its validations, exceptions, interfaces and acceptance tests. Ainna's FRS traces each of these to the PRD, and its architecture document carries the quality targets. **What is the difference between a BRD and an FRS?** A business requirements document (BRD) states what the business needs and why, in the business's own terms. An FRS turns those needs into exactly how the system must behave, testably, for the people who build and test it. In banking, insurance and enterprise IT the two usually come as a pair. In Ainna, the PRD plays the BRD's part, with the business case, the users and the requirements, and the FRS traces every requirement back to it. **What goes into a software architecture document?** Ainna's covers the system in context and its logical architecture, both as diagrams; the components and their responsibilities; how it integrates with other systems; its data and where it is stored; quality attributes with targets; security; deployment and recovery objectives; and the key architecture decisions with their alternatives. **Do the documents agree with one another?** Yes. They distil the same work: the problem framing, the personas, the market, the business model and the plan. The FRS traces every requirement back to the PRD, and the architecture document is drawn from the same system model as the FRS. **How are the documents designed?** Every document is architected and designed for one purpose: clarity. The designs are original, built on the method of Innovation Mode 2.0 by George Krasadakis (Springer Nature, 2026), where some of them are published. Ainna distils your work into each one. **Are these real examples?** Every page shown was rendered by Ainna's document engine, all for one idea, VentureForce, which Ainna developed for a real problem on Problem Radar. The problem's figures come from the sources it cites; VentureForce is a concept, not a company, and its market figures are AI estimates. **Where should I start?** With the problem. Frame it, run a brainstorm, and the idea's one-pager and pitch deck follow. When you are ready to build, the PRD comes first, and the FRS and the architecture document rest on it. ## Start with a problem Great work deserves great presentation. Work a problem through with Ainna and these documents come out of the work, written from your own analysis. Take a real problem from Problem Radar, the one these samples began with or another, or bring your own: https://ainna.ai/ - [A workforce unprepared for the disruption AI is bringing](https://ainna.ai/problems/workforce-unprepared-for-the-disruption-ai-is-bringing) (Problem 0032, Work, where these samples began): AI is changing work at several levels at once. - [Unverifiable AI answers](https://ainna.ai/problems/readers-cant-check-the-ai-answer-they-were-given) (Problem 0012, Media): Use of AI assistants for news is rising while stated trust in them stays very low: people take answers from a source they openly doubt, because it is faster than the alternative. - [Invisible small-firm credit](https://ainna.ai/problems/small-firms-cant-prove-a-trading-history-lenders-accept) (Problem 0007, Finance): Small firms are assessed on documents they were never required to produce. - [Grid connection backlog](https://ainna.ai/problems/energy-developers-are-blocked-by-paperwork-not-engineering) (Problem 0002, Energy): The constraint on the energy transition moved from manufacturing to administration, and no tooling followed it. - [A widening cyber-security gap between big and small firms](https://ainna.ai/problems/small-firms-face-enterprise-attacks-without-a-security-team) (Problem 0009, Enterprise AI): AI has made cyber attacks cheap to run and easy to scale. - [No AI-exposure offramp](https://ainna.ai/problems/workers-cant-move-out-of-the-roles-ai-reaches-first) (Problem 0010, Work): We can now say with some precision which occupations generative AI reaches first, how that varies by country, and that the exposure falls hardest on clerical and administrative work done mostly by women. - [Digital identity exclusion](https://ainna.ai/problems/people-without-id-lose-the-services-that-moved-online) (Problem 0013, Public sector): Benefits, banking, health records and school places are moving to interfaces that begin by asking you to prove who you are online. - [Doctors uncertain which antibiotics still work where they practise](https://ainna.ai/problems/doctors-prescribe-antibiotics-without-knowing-what-works-locally) (Problem 0005, Health): When a patient has an infection, the doctor, nurse or pharmacist has to choose an antibiotic that will work, and which ones still work depends on the place: resistance differs between countries and regions, and it is growing. - [Unverifiable student work](https://ainna.ai/problems/teachers-cant-tell-who-learned-and-who-prompted) (Problem 0011, Education): Most institutions are writing or planning a policy about AI; few have changed what they actually measure. The whole Index: https://ainna.ai/problems ## About the samples Every sample page comes from one public problem, number 0032 on Problem Radar, [AI is restructuring jobs, firms and markets faster than economies can adjust](https://ainna.ai/problems/workforce-unprepared-for-the-disruption-ai-is-bringing), which Ainna framed and developed into one idea, VentureForce. It is a concept, not a company; its market figures are AI estimates. The pitch deck was made on Ainna; the other eleven documents were rendered by Ainna's document engine and templates from the same idea's data.