SALES PROPOSAL / HARUKA WORKS
Less effort on the document.
Improve the sales-document workflow · A four-week pilot
Keep the quality. Reduce repeated work.
An illustrative proposal for the fictional company Haruka Works.
Research, drafting, review and layout are split across people. The same checks are repeated before a proposal reaches the customer.
Where could we first reduce repeated work?
In this fictional dataset, inquiries rise from 120 to 240; proposals from 52 to 78. These are assumptions for discussion, not real results.
Keep content, data and design in local files. Review them together before exporting the proposal.
AI can support a draft. People check the facts and make decisions.
Current: 12 hours. Pilot target: 7 hours per proposal. The five-hour difference is an assumption to test over four weeks, without skipping review.
Drafting: 4 hours. Research: 3. Review: 3. Layout: 2. Start by reusing drafts and reviewing changes in the source.
| Area | Illustrative current state | Pilot approach |
|---|---|---|
| Evidence | Copy into each document | Keep CSV / JSON nearby |
| Content | Review the finished file | Read Markdown changes |
| Design | Format every time | Reuse CSS |
| Quality | Manual visual check | Human review + validation |
Evaluate workflow fit and the learning effort as well as time saved.
WworPoint includes no AI model. Vega-Lite and Mermaid generate the visuals; validation and export happen locally.
| Week | Milestone | Owner | Check |
|---|---|---|---|
| 1 | Baseline agreed | Sales ops | Measurement method |
| 2 | Test one proposal | Sales rep | Content and evidence |
| 3 | Fix review steps | Sales lead | Changes and reproducibility |
| 4 | Review and decide | Pilot team | Quality maintained |
Start with one proposal theme. Review the results before expanding.
NEXT STEP / A SMALL, REVIEWABLE START
Improve the process together.
Proposed decision: begin a small four-week pilot.
A fictional proposal. No time-saving or ROI guarantee.