Accelerator catalogueHow we buildProduct storiesAbout SparrofoxDiscuss a process
MergeHawk · Browser document preview

See job details become a document.

Open the browser example, change fictional job details and compare the sample output.

Client-side HTML preview · fictional data. No CRM connection, approval or sending. The local Word example below is separate and not deployed.

Actual browser screen · fictional sampleActual MergeHawk browser example with fictional job fields and its sample job-summary document
Compare the fictional job details with the document they produce in the browser.
Open full-size screenshot ↗

Inside MergeHawk

Design the document.
See the result.

Actual app screens · fictional local examples

Merge fields, optional sections and charts, with a Word preview beside your design. Take a closer look at three sample documents and the tools used to build them.

What these examples show

Field-based optional sections, bar/line/pie chart settings and charts embedded in a Word document. The designer and document previews shown here ran using invented names and values.

Start with one document

These screenshots demonstrate the app locally. Your data source, document requirements and access need to be checked for your setup. The examples do not represent customer results, photo handling or a completed customer integration.

Try the separate browser sample ↗See the separate samples ↗Back to the product showcase

The browser sample uses fictional HTML output. These designer screenshots show locally rendered Word previews; Word pagination and your template’s output need separate review.

One document family, then agreed adaptation

One document family, one approved information source and necessary related items, an agreed human review point and one internal output destination.

Fictional illustration — not customer proof

Example: turn quote details into a document to review

Where a confirmed gap remains, an agreed document workflow could assemble approved customer, job and line-item information into a quote template for a person to review. Discovery first checks whether the current software can already do the job.

Job
Replace a damaged gate latch at Example Job 01.
Scope
Remove the old latch, fit the replacement and check it closes.
Exclusion
Gate and hinge repairs are outside this scope.

One document family, one approved information source and necessary related items, an agreed human review point and one internal output destination.

This is an illustrative starting point. It is not an automatically approved quote, a deployed customer workflow or a send action.

Discuss one document workflow

What you start with

A named accelerator or process design, its intended job, the starting deliverable and the limits to check. The catalogue shows whether it is a foundation to assess, a package design, a preview or research.

What we agree for your business

Your data, current tools, configuration, connections, review steps, rollout and handover. The agreed scope states what is included, what is excluded and how you will accept the result.

Agree the next scoped step

Discovery, implementation, licences, usage and optional support are agreed separately.

1. Explore and discuss

Find a relevant foundation and one process. Explore what it covers and its readiness, then check the fit against your current tools.

2. Agree discovery

Agree a paid discovery to examine one process, compare your current approach and define the deliverable, fit and acceptance criteria.

3. Approve implementation

Approve a separate implementation scope and price before configuration or adaptation begins. Your team reviews the agreed output before handover.

4. Handover and optional support

Your team reviews the agreed output and receives the agreed training and operating guidance. Ongoing support is optional and separately agreed. Product licences, third-party licences and usage costs are listed separately.

Illustrative calculation only. Adjust the sample assumptions to discuss a workflow. Any “after” output is a hypothetical target, with formats, review, delivery and timing to agree.

// document workflow diagnostic

See the document work hiding inside Dynamics.

Choose the buyer closest to the problem, then adjust three bounded inputs. The result is directional—not a promised saving—and gives the pilot a concrete workflow to prove.

Before · copied documents65 hrs

Approximate staff time touched each month, including a transparent 30-minute allowance for each corrected document.

After · one governed flow1 flow

A Dynamics quote flow with mapped fields, conditional commercial clauses, approval evidence, and a controlled PDF or Word destination.

Sales operations proof

Prove one quote or proposal path where account, opportunity, product and approval data currently gets copied by hand.

Carry this result into Start →

Calculation: documents × manual minutes, plus 30 minutes for each document likely to need correction. It estimates workflow exposure only; any pilot scope, output checks and timing must be agreed separately.