Salesforce closes the deal.
LinePDF gets it paid.

No. Setup is point-and-map: pick your object, map your fields, choose a template. All clicks, nothing to code. Templates ship ready to run, and generating a document from a Flow is a ready-made action you drop in like any other element. When you want a custom layout, you describe it and an AI writes the template (Claude, Agentforce, or ours). LinePDF is built for teams that don't have a Salesforce developer and don't want to hire one for their invoices.

The package is in Salesforce's security review for a free AppExchange listing. Reviews run on Salesforce's clock, not ours (the queue runs weeks, with a resubmission cycle roughly half of all packages go through), so we won't promise a date we don't control. The early-access list gets the install link first, before the listing goes public, along with the security one-pager to hand your admin. Join it from the pricing section.

Because the package hasn't cleared Salesforce's security review yet; it's in review now for the AppExchange listing. Until it clears, every direct-URL install of any package shows that warning. We don't hide from it: install into a sandbox first with the security one-pager open and read exactly what's in the package before it touches prod. The Apex makes zero callouts; you can verify that in the code.

No. Rendering is 100% native Apex inside your org. There are no external callouts, no OAuth scopes, no connected apps, and no ShareCo servers in the data path. We never see a byte of your customer data. The only data we hold is what you send us by email or through this website's contact form.

Two ways. First, the line-item engine: per-line tax, per-line discount, section grouping, and totals that cross-foot, which is exactly where generic merge loops break (it's the #1 complaint in incumbent reviews). Second, pricing: flat $49/org/month with no per-seat fees and no contract minimums, against incumbents that start around $3,000/yr. They're capable products when your documents are simple. Ours earns its keep when the math has to be right.

They're genuinely good, and if your documents are simple, use them. LinePDF exists for the documents they render wrong: stacked discounts, mixed tax rates on one document, section subtotals that have to reconcile with CPQ math, change-order deltas. If a generic merge loop handles your docs, you don't need us.

Any parent object with child line records, standard or custom. Five templates ship ready to run: quote, invoice, PO, packing slip, and change order, mapped to standard objects and easily re-pointed at custom ones. The template declares its object and line source; the engine does the rest.

Yes, that's the design constraint the template format was built around. A template is plain, readable HTML with merge syntax, stored in a text field on a custom object in your org. There is no binary format and no GUI builder lock-in. Claude or Agentforce can read your current template, modify it, and write it back. Pro includes the prompt kit and schema docs that make this reliable.

Built and running today: the line-item engine, templates, themes, and every automation entry point (Flow, REST, Agentforce). Shipping with the AppExchange listing: the get-paid layer, meaning e-delivery with open tracking, Stripe payment links on invoices (your own Stripe account; keys live in your org, never on our servers), automated payment reminders, and paid-status writeback. The pricing section marks which is which; we won't sell you a tier whose features don't exist yet.

Your documents keep generating. The package runs entirely in your org, the templates are plain text you own, and any Salesforce developer can read them. There is no license server in the render path and no dependency on us being alive. That's deliberate.