← Back to blog

Stop Rebuilding Your Estimate as a Proposal

You finish the estimate. The deal's phases, roles, hours, and rates are all correct, line by line, after however many rounds of adjustment it took to get there. Then you open a blank document to write the proposal, and none of that comes with you.

Every firm has some version of this seam: the numbers live in one tool and the words live in another, and somebody reconciles them by hand before a client ever sees either one. That reconciliation step, not the estimate itself, is where small errors get introduced. A phase gets renamed in the document but not the budget. A role count changes after a review comment and the proposal quietly goes stale. The estimate is usually the most carefully checked number in the deal. The document built from it, by hand, afterward, is not.

The handoff that was never built

Charter is JungleOS's document generator, and its job is narrow on purpose: generate a proposal or statement of work from a scope estimate you've already built and approved. The deal, its financials, its phases, roles, and timeline flow into the document through merge tags, so what's in the SOW is what was actually scoped, not a retyped summary of it written by whoever got stuck with that task on a Friday afternoon.

That's the whole premise. Not a smarter editor, not a nicer template library on top of the one you already have. A document that can't drift from the number it came from, because it's generated from that number, not copied from it.

Your firm's document, not a template

A SOW that looks like every other vendor's SOW is a cost, not a feature: it reads as commodity work, and most firms have spent years building the actual language, structure, and cover treatment that signals this proposal came from them specifically. Charter's layouts and clause library are firm-owned, with rich text, tables, images, and cover graphics authored once and reused.

Clauses can be set to appear only when the matching scope is actually in the estimate, so a firm with ten service lines doesn't ship a forty-page document to a client who bought one of them. Per-phase sections repeat automatically for each delivery phase, each carrying its own content, so a three-phase engagement gets its own testing section three times without anyone copying and pasting it three times.

The tables you used to build by hand

The methodology timeline and the payment schedule generate directly from the estimate and its deal modeling data, instead of getting rebuilt in a separate spreadsheet and pasted in as an image. Tables that don't come from the estimate, a RASCI matrix is the common example, are authored once in the layout and stay there.

Outline numbering and the table of contents update automatically as sections are added or reordered. Where a layout asks for something Charter can't resolve, it raises an authoring warning instead of silently dropping the section, so the gap shows up while you're building the document, not after a client has it.

Still runs through the approval your estimate already has

A proposal that skips your firm's own review process to go out the door faster isn't saving time, it's moving the risk downstream. Charter's document approval reuses the same approvers and approval levels already configured for the estimate. Approval history shows who signed, when, and who it's still pending with; submitters and approvers both get notified; and "approved by" and "approved on" can print directly into the document if your firm wants that on the page.

Every generation is also a stored, named version with its own history, so knowing which draft is current doesn't depend on a filename convention or the last reply in an email thread.

What it doesn't do

Once a document is exported, negotiation and redlining happen outside Charter. That's a deliberate line, not a gap: contract markup with a client is a different job with different tools, and trying to own it inside the document generator would mean half-building a second product. There's no AI-written SOW narrative and no e-signature inside Charter either. Comparing two versions of a generated document side by side isn't there yet; today you have the stored version history, not a diff view.

Live preview and Word export mean you're reviewing the actual document before it leaves the firm, which is the review that matters most. Charter is priced at $59 per month per user on top of an active Scope subscription, with the first seat included, and every Charter user is also a Scope user, since the two stay in lockstep by design.

The estimate was already the hard part: getting the scope, the roles, and the hours right for a specific client. Writing it a second time, by hand, into a separate document, was never supposed to be the second hardest part of the deal. Now it doesn't have to be.