Central shell
Launcher
Launcher is the shared shell for settings, license state, logs, and module access. Keep it visible, but secondary to the two real working paths below.
DocxForge Pro
DocxForge Pro is a Windows document automation suite for two clear jobs: controlled document assembly and high-volume production. Contractor handles reviewed case workflows and can also load case data from Excel, while Factory is optimized for Excel batch generation. Your .docx templates stay in control while DocxForge fills text tags, inserts photo tags, manages filenames, and can export PDFs locally through Microsoft Word Desktop.
Current suite demo
Release includes Contractor and Factory - local Word/PDF output.
Launcher is the shared shell, but the real choice is simple: use Contractor when you want reviewed, per-case document work, or use Factory when you want fast Excel-based production. Excel fits both workflows.
Launcher is the shared shell for settings, license state, logs, and module access. Keep it visible, but secondary to the two real working paths below.
Best when you need structured fields, reviewed case data, controlled edits, and per-case generation. Contractor can also start from case data loaded from Excel when a reviewed workflow makes more sense than a raw batch run.
Best when you need Excel-driven production: larger runs, naming rules, photo folders, batch-size control, and optional PDF export after Word generation.
Planned as the next layer of the suite for AI-assisted analysis and document intelligence. Keep it marked as coming later, not as a live reason to buy today.
Both live modules keep your Word template in control. DocxForge fills text tags like {{ClientName}}, inserts photo tags like {{photo}}, and supports special image tags such as {{photo_logo}}, {{photo_signature}}, and {{photo_stamp}}.
Factory can generate Word documents and optionally export PDF locally through Microsoft Word Desktop. Contractor is better when you want controlled review before final output.
Excel is useful in both workflows: Factory runs straight from Excel tables, and Contractor can load case data from Excel when you want controlled review before generation.
Same suite, two live document paths, and one AI layer that is still planned.
Open the suite, review shared settings, check logs or license state, and then move into the workflow that matches the job.
Use Contractor for structured case work, reviewed fields, controlled edits, and per-case generation. It can also load case data from Excel when that makes review easier.
Use Factory for Excel batch production with naming rules, photo folders, batch-size control, and optional PDF export.
The AI Module belongs in the roadmap, but it is still in development. Keep the current buying decision focused on Contractor and Factory.
Eight current product pillars, with Excel-friendly inputs, tag logic, photo handling, and local output made explicit.
Shared entry point for settings, license state, logs, and module access.
Structured case review, controlled edits, and per-case document generation.
Excel batch runs, naming rules, photo folders, and high-volume output.
Factory runs from Excel tables, and Contractor can also load case data from Excel.
Your .docx template keeps layout while DocxForge fills matching text tags such as {{FieldName}} locally.
Photo lookup supports {{photo}} plus dedicated logo, signature, and stamp image tags.
Word documents first, with optional local PDF export through Word Desktop.
A local Windows alternative for teams that outgrow basic Excel-to-Word mail merge.
The 3-month plan includes a 7-day free trial. All paid plans include Launcher, Contractor, and Factory, and all purchases are covered by a 14-day refund policy.
All paid plans include Launcher, Contractor, and Factory. Factory is optimized for Excel batch runs, and Contractor can also work with case data loaded from Excel.
Best for a short run, an urgent job, or a quick first paid use without a longer commitment.
Best first paid term for setup, testing, and real production use.
Best when DocxForge becomes part of an ongoing workflow and you want the lowest monthly cost.
Best when you want the longest access window and fewer renewals.
| Plan | After trial | Effective monthly | Best for | Action |
|---|---|---|---|---|
1 month Short-term use |
$19 monthly | $19.00 / month | Short jobs and quick paid runs | Subscribe monthly |
3 months Main starter plan |
$38 every 3 months | $12.67 / month | Best first paid term | Start Free 7-Day Trial |
1 year Lowest monthly cost |
$79 yearly | $6.58 / month | Recurring production workflows | Subscribe yearly |
2 years Longest access window |
$159 every 2 years | $6.63 / month | Longer rollouts with fewer renewals | Subscribe 2 years |
Short answers for the current suite.
Yes. Document generation runs locally on your PC. There are no cloud uploads. Internet may be used only for license verification.
Launcher is the shared entry point for Contractor and Factory, plus shared settings, license state, and logs.
Use Contractor for structured case workflows, field review, controlled edits, and per-case document assembly.
Yes. Contractor can work with structured case data, including case data loaded from Excel when a controlled review workflow is a better fit than a raw batch run.
Use Factory for Excel-based production runs with naming rules, photo handling, and optional PDF export.
Yes. Word Desktop is required for template processing and PDF export. Word Online is not supported.
Images can be resolved by full path, filename, or base name. Standard photo tags such as {{photo}} can place regular images, while {{photo_logo}}, {{photo_signature}}, and {{photo_stamp}} use dedicated local rules.
Text placeholders use standard tags such as {{ClientName}}. Factory maps Excel headers to matching tags, while Contractor fills the same template structure from case data. Photo tags can be regular image tags or dedicated image tags such as {{photo_logo}}.
No. The current release is Launcher, Contractor, and Factory. The AI Module is still in development.
Plans start at $19 per month. The main starter package is $38 for 3 months, with annual and 2-year terms also available.
Start with the 3-month plan: 7 days free, then $38 every 3 months.
The most common reasons first runs go wrong.
Contractor and Factory solve different problems. Do not force a schema-heavy workflow into Factory or a large production run into Contractor.
When the workflow depends on Excel-to-template mapping, headers must match Word tags exactly. Hidden spaces and mismatched names break replacements.
Do not split a tag across different formatting runs. Type the full tag first, then apply styling if needed.
Close Word and Excel before generation to avoid file locks, stale previews, or unpredictable export behavior.
If multiple images share the same name inside your photo search scope, auto-detection can pick the wrong file. Keep filenames unique, including subfolders.
If {{photo}} or special image tags such as {{photo_logo}} do not resolve to a real file, the output will be incomplete. Always test with a small sample first.
If naming rules are not set clearly, files can become hard to review or overwrite each other during larger runs. Define output names before scaling up.
Do not start with the full dataset. Test a small batch first to confirm tags, photo resolution, output names, and PDF export before scaling up.
Company information in accordance with legal requirements.
Legal Name: Asko Trade OÜ
Registration Number: 14462595
Registered Address: Männimäe, Pudisoo küla, Kuusalu vald, Harju maakond, 74626, Estonia
VAT Status: Not registered (below the mandatory threshold in Estonia).
Email: support@docxforgepro.com
LinkedIn: DocxForge Pro
Business Activity: Development and distribution of local document automation software. We specialize in Windows-based document workflows, schema-driven document assembly, and Excel-powered Word/PDF production.