A4 proposal / Page 1 source
Source for page 1 of 5 of the actual generated example. Companies, metrics and proposals are fictional. This excerpt is not a standalone document: it needs the shared theme, configuration and referenced files.
Markdown for this page
Section titled “Markdown for this page”An excerpt of document.md, split at its explicit page boundary. Separate fixed pages with <!-- wwpo:break -->.
document.md
Section titled “document.md”<!-- wwpo:page flow=fixed -->
# Improve proposal production
**For Haruka Works / A four-week pilot proposal**
This is an illustrative proposal for a fictional company. Customer information, business results, metrics, costs and expected benefits are invented. They are not real company results or evidence of WworPoint's effectiveness.
## Executive proposal
We consider a fictional situation in which growing inquiries put pressure on the time available to create proposals. For four weeks, test a workflow that keeps content, evidence and design in files, with a consistent path from review to export.
> The aim is not only to work faster, but to make evidence and changes easier to check.
## The assumed challenge
The baseline assumes 12 working hours per proposal. Transcribing information, adjusting layout and comparing finished files take time. Improvement may be possible, but the team first needs a shared measurement method.
## Scope and participants
Use one proposal theme and its reviewers. Manage Markdown, local CSV/JSON, CSS and visual definitions. Moving customer information outside the organization or connecting business systems is outside this example's scope.
## Requested decision
Approve a four-week pilot and set aside time for weekly reflection. Consider wider adoption only after reviewing the results.Referenced visuals and data
Section titled “Referenced visuals and data”This page has no external chart, diagram or CSV references. Any inline table is included in the Markdown above.
Design and reproduction
Section titled “Design and reproduction”Headings, spacing, color, tables and page footnotes use the shared CSS and business preset. Page directives and visual definitions shown above also affect the output. The source ZIP on the example overview contains the complete document and required files. Save changes, then preview, validate and export to check them.