Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@dealdesk

Po creator

@dealdesk/po-creator

Turn a deal into a clean order form or purchase order, in markdown and printable HTML. Computes line totals, discounts, contract value, and a billing schedule, and lists what finance needs before signature. Works offline from a JSON file or a short text form.

SkillRevOpsv1.0.0 (latest)Tested
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1---
  2. 2name: po-creator
  3. 3description: Turn a closed or closing deal into a clean order form or purchase order (markdown and printable HTML) with line totals, discount math, contract value, a billing schedule, and a checklist of what finance needs before signature. Use when the user says "make an order form", "draft the PO", "write up this deal for signature", "paperwork for the Northwind deal", or pastes deal terms (customer, products, prices, term, start date, payment terms). Works from a JSON file or a short text form, with any CRM.
  4. 4license: MIT
  5. 5---
  6. 6
  7. 7# Order form and PO creator
  8. 8
  9. 9Turns deal terms into a document a customer can sign and finance can bill from. The script does every calculation, so the numbers are exact and the same every time. You collect the terms, run it, and walk the user through the checklist.
  10. 10
  11. 11## When to use
  12. 12
  13. 13- A rep or deal desk needs an order form or purchase order for a deal.
  14. 14- The user pastes deal terms from a CRM, an email, or a quote and wants it "ready to sign".
  15. 15- Not for contracts or MSAs. Those are legal documents; this produces the commercial order that sits under them.
  16. 16
  17. 17## Inputs
  18. 18
  19. 19Ask for anything missing. Never invent a legal name, address, price, or PO number.
  20. 20
  21. 21| Field | Notes |
  22. 22| --- | --- |
  23. 23| Customer legal name | Exact registered name with suffix (Inc., LLC, Ltd., GmbH) |
  24. 24| Billing address and billing contact | Contact can be a team ("Accounts Payable") plus an email |
  25. 25| Products | SKU, description, quantity, list price, net price; mark one-time fees |
  26. 26| Term and start date | Months, and `YYYY-MM-DD` |
  27. 27| Billing frequency and payment terms | `annual` (default), `quarterly`, `monthly`, `semi-annual`, `upfront`; `Net 30` default |
  28. 28| PO required? PO number? | Many larger customers will not pay an invoice without their PO number on it |
  29. 29| Signer, tax ID, order number | Optional, but flagged when missing |
  30. 30
  31. 31Recurring prices are per unit per year. Add `"price_period": "month"` (or `| month` in the short form) for monthly unit prices.
  32. 32
  33. 33## Steps
  34. 34
  35. 351. **Collect the deal.** If the user gave a file in `data/`, use it. Otherwise write `data/deal.json` (shape: the kit's `examples/deal.json`) or `data/deal.txt` in the short form:
  36. 36
  37. 37 ```text
  38. 38 customer: Contoso Robotics Inc.
  39. 39 address: 22 Harbor Road, Bayview
  40. 40 billing contact: Finance Team, invoices@contoso.example
  41. 41 start: 2027-01-01
  42. 42 term: 24 months
  43. 43 billing: annual
  44. 44 payment terms: Net 30
  45. 45 po required: no
  46. 46 line: PLAT-SEAT | Platform seat | 120 | 600 | 510
  47. 47 line: ONB-PLUS | Onboarding plus training | 1 | 9000 | 9000 | one-time
  48. 48 ```
  49. 49
  50. 50 Show the user the terms you captured and ask them to confirm before generating.
  51. 51
  52. 522. **Generate.**
  53. 53
  54. 54 ```bash
  55. 55 node scripts/po-creator.mjs data/deal.json --out out --name order-form
  56. 56 ```
  57. 57
  58. 58 Use `--name` to give each deal its own files, for example `--name of-2026-0142`. Add `--today YYYY-MM-DD` only to reproduce an old run.
  59. 59
  60. 603. **Read the summary** in `out/<name>.json`: `totals`, `billing_schedule`, `checklist`, `blockers`.
  61. 614. **Report back** with the template below. Lead with blockers.
  62. 625. **Fix and rerun.** When the user supplies a missing item (PO number, signer), update the deal file and run step 2 again. Never hand-edit numbers in the output files.
  63. 636. **Hand off.** The HTML prints cleanly to PDF from any browser (File, Print, Save as PDF). The finance checklist prints on its own last page and is marked internal: remind the user to drop that page before sending.
  64. 64
  65. 65## Output to the user
  66. 66
  67. 67```markdown
  68. 68**Order Form OF-2026-0142** for Northwind Traders LLC: TCV $34,000.00, ACV $30,000.00, discount 17.1%.
  69. 69Files: out/order-form.md, out/order-form.html (print to PDF)
  70. 70
  71. 71Before signature (1 blocker):
  72. 72- BLOCKER: customer requires a PO and none is recorded.
  73. 73- Payment terms Net 45 are past Net 30: needs finance approval.
  74. 74- Signer name and title are missing.
  75. 75
  76. 76Billing: 4 quarterly invoices, first one $11,500.00 on 2026-12-01 (includes onboarding).
  77. 77```
  78. 78
  79. 79## Checks the script makes
  80. 80
  81. 81- Blockers: missing legal name, address, billing email, start date; PO required but no PO number; zero or negative quantities.
  82. 82- Warnings: no entity suffix on the legal name, start date in the past, payment terms past Net 30, overall discount above 20%, net above list, missing signer.
  83. 83- Info: no tax or VAT ID, no order number, vendor onboarding forms.
  84. 84
  85. 85If the discount or terms look non-standard, suggest running `discount-approval-check` (same deal file) before sending.
  86. 86
  87. 87## Guardrails
  88. 88
  89. 89- Never fill in a legal name, PO number, tax ID, or price the user did not give you. Leave it missing and let the checklist flag it.
  90. 90- Never send the document to anyone. The user sends it.
  91. 91- Do not add legal terms, warranties, or SLAs to the order form. If the user asks, say those belong in the contract and suggest they reference it by name.
  92. 92- Currency is one per document. If the deal mixes currencies, stop and ask.
Sign in to comment on a line