Enterprise DNA

Instead of Conga Composer

Stop renting Conga Composer. Own your document generation.

We build your version around the documents your business produces, bring your Conga Composer records across and run it for you. Start with the wording, fields and review steps your team already uses.

Conga provides tailored pricing. Compare your current quote with a document system your business owns.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What your subscription covers

Which parts of Composer does your team actually need?

Conga Composer combines template-based documents, business records and connected delivery. If your weekly work is a repeatable set of letters and confirmations, scope your own version around those jobs.

paid

A tailored subscription quote

Conga asks for your requirements before providing pricing. Bring the actual renewal quote so the comparison starts with what your business pays.

description

Template-driven documents

Composer fills reusable wording from business records. Your own version keeps approved wording and every revision alongside the jobs that use it.

dataset

Records merged from business systems

Composer pulls information from connected sources. Start your move with an exported data workbook and reconcile the fields before producing a document.

picture_as_pdf

Several output formats

Composer produces Word, PDF, spreadsheet and presentation documents. We agree which exact formats and layouts your custom version must produce.

event_repeat

Repeat production

Composer supports bulk production and triggers. Your own version starts with an operator-reviewed queue of recurring documents and their due dates.

link

Connections and distribution

Composer can send and store documents through connected systems. We scope those connections around your business, with review before delivery.

Your own document desk

Know what is due, what is approved and what changed

The weekly queue

Give every document an owner and a date

A confirmation and a renewal need different wording, but both need a person responsible for the next step.

  • check List open jobs in due-date order.
  • check See overdue work beside the template holding it up.
  • check Compare the week’s workload by owner.
  • check Draft a Monday review from the queue and missing evidence.

Reviewed wording

Keep decisions with the exact version

A template change starts a fresh review. An old approval does not silently carry forward to new wording.

  • check Save each wording revision with its editor and reason.
  • check Record a different reviewer and supporting evidence.
  • check Set a review date for each approved version.
  • check See which open jobs are blocked by an overdue template review.

Reliable drafts

Find missing fields before producing the document

The free version merges literal fields and repeated detail rows, then saves a printable draft with the records used to create it.

  • check Import a Composer data workbook after checking its structure.
  • check Reject incomplete merge fields before generation.
  • check Save the wording version and source records with each draft.
  • check Find outputs made from records that have since changed.

Evidence and ownership

Make information checks part of production

Keep purpose, accuracy evidence and retention decisions beside personal-information jobs. These are recorded checks for your operator to review.

  • check Require an accuracy check for the current record version.
  • check Flag retention decisions, including archived jobs.
  • check Keep a local decision on the exact generated output.
  • check Export the complete history from a database your business owns.

Make it yours

Design your own Conga Composer replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Conga Composer. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Conga Composer replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Conga Composer data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Document Generation for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Document Generation for Claude Code

Connected to your own database

Which documents need our attention this week?

Harbour account summary

Mplate ow
Account summary
Ner du
Aroha Chen
E_date re
2026-10-17
Adiness pr
needs approval
Ivacy ou
unknown
Tput_count
0

Harbour service confirmation

Mplate ow
Service confirmation
Ner du
Aroha Chen
E_date re
2026-10-19
Adiness pr
ready
Ivacy ou
personal
Tput_count
0

Westhaven service confirmation

Mplate ow
Service confirmation
Ner du
Aroha Chen
E_date re
2026-10-23
Adiness pr
ready
Ivacy ou
business
Tput_count
0

Summit renewal

Mplate ow
Renewal letter
Ner du
Mia Wilson
E_date re
2026-10-24
Adiness pr
review overdue
Ivacy ou
personal
Tput_count
0

Ask it anything

Questions to ask across your document work

These ten questions run against the included fictional records. They combine your production and review rules in one place.

chat_bubble Which overdue jobs also lack an approved template?
chat_bubble Who has the most overdue documents?
chat_bubble Which templates block the most open jobs?
chat_bubble Which personal-information jobs need an accuracy check?
chat_bubble Which archived jobs still need a retention decision?
chat_bubble Which outputs use superseded data or wording?
chat_bubble Which outputs are waiting for review?
chat_bubble Which jobs are repeatedly generated?
chat_bubble Which imported jobs have never produced an output?
chat_bubble Which open jobs have missing merge fields?

Switching

How to switch from Conga Composer

The move usually means exporting the records and templates you need, mapping them into the database, then checking new drafts alongside your current process before you stop using Conga Composer.

  1. 1

    Export your Composer data

    For Composer for Salesforce, download the solution’s View Data Workbook, which contains the records retrieved for that solution. Each workbook provides one master record and its repeated detail datasets. Also gather the templates you need to move. If your account does not provide this workbook or you use a different Composer setup, check with Conga and export what your account allows, usually CSV or Excel.

  2. 2

    Preview the import

    Register a text or DOCX template with literal merge fields, then load a workbook using the import preview before you make changes to the database. The preview lets you check the import first. Have the person responsible for your documents confirm the master record, repeated detail groups, template and job information are matched to the right business purpose.

  3. 3

    Review import issues

    Check the preview and import results for records or fields that need attention. Compare the imported records with the workbook you exported, and look for missing merge fields or details that did not map as expected. Check the document wording too. Template extraction preserves paragraph text and literal fields, not the original Office layout or arbitrary Word field instructions, so some templates need adapting.

  4. 4

    Run both processes side by side

    Keep your current Conga process in place while an operator checks the new process on representative documents. Compare the records used, wording and generated drafts with the examples you already trust. Resolve differences in fields, rules or templates before moving more work across. The new system saves drafts for review and does not include automatic delivery, so keep your existing delivery process in mind.

  5. 5

    Switch off Conga Composer

    When the documents you agreed to move have passed your checks, stop using Conga Composer for those workflows. Keep the records, templates and evidence you need according to your business requirements. Before ending your Conga setup, make sure you have retained any history you still need. Source permissions do not transfer to the new system, so plan access and handling for the imported data.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules, adapting templates and deciding how much history to bring across. The workbook import covers a master record and repeated detail datasets, but layouts, special fields and source connections may need attention. If Enterprise DNA installs and runs your version, Enterprise DNA handles this mapping and migration work as part of the move.

Not ready for a call?

Get your Conga Composer switch plan by email

We will send you the step-by-step plan for moving your business off Conga Composer, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want us to handle

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, npm test and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Try the document queue and generate the fictional service confirmation.
  4. 4 Register your template, preview a Composer workbook import and check the draft.
Get it on GitHub

Built around your business

We customise it

A setup fee, then a retainer

  • check Your wording, fields, approval steps and exact document formats.
  • check Your Conga Composer records mapped and checked against the export.
  • check A web front end and connections where your team needs them.
  • check Your choice of technology and a system your business owns.
Build our version

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA.
  • check Your document queue connected to agreed business systems.
  • check Access controls, backups and review responsibilities set for your team.
  • check Ongoing changes as your documents and business rules evolve.
Get your version built

Questions

Instead of Conga Composer, answered

Will this reproduce every document we make in Conga Composer? expand_more

We start with your actual document list and a known example of each. The free version produces printable drafts from literal fields and repeated rows. Enterprise DNA builds your exact Word or PDF layouts, images and connected workflows into the agreed custom version.

Can we bring our existing templates and records across? expand_more

Composer for Salesforce provides a View Data Workbook containing the records retrieved for a solution. The free version imports one master record and its detail groups from that workbook. Word template import extracts paragraph text and literal fields. We check and adapt your layouts, special fields and source connections as part of the move.

What stops an old template or a wrong recipient reaching a customer? expand_more

Generation requires a reviewed current template and complete fields. Personal-information jobs also need recorded accuracy evidence. A different reviewer label records the output decision. The free version keeps everything as local drafts. In your managed version, we design identity checks and delivery approval around your team.

Does a clean compliance report mean our business is compliant? expand_more

No. It shows recorded evidence and overdue decisions. The included checks reference New Zealand privacy principles for accuracy and retention, alongside your own template-review rules. Your operator decides what evidence is sufficient and which retention obligations apply.

How does Enterprise DNA charge for our version? expand_more

One setup fee, then a retainer. We scope the document formats, migration, connections and ongoing operation around your business. Bring your current Conga Composer quote and a few representative documents so we can compare the actual work.

Bring the renewal quote and the documents you produce every week

Spend 30 minutes with Sam. We look at your Conga Composer bill, the documents your team relies on and the review steps they need. You leave knowing what your own version would cover and what Enterprise DNA would build and run.

Document Generation for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Conga Composer?

Get your version built