What custom PDF and Excel automation costs: how an itemized one-time quote is built

Buyers ask for a price before they send files. We understand why. We still need sample documents before the final number is honest. What we can publish are typical one-time implementation ranges and the factors that move a job between them. The live tables also sit on our PDF and Excel workflow automation page. This post expands the reasoning behind those tiers.

If you only need a sense of whether the work is Starter-shaped or Custom-shaped, the tiers below are enough for a first conversation. If you need a number you can put in a purchase request, send samples and we itemize.

These are typical starting ranges, not fixed prices. The actual price depends on your workflow and is confirmed in an itemized quote after we see your sample files.

Typical one-time ranges

Starter: Rs 12,000 to Rs 18,000

Rough fit when you have 1 to 3 document formats, about 20 to 25 fields in total, and inputs that are PDF, CSV, Excel, or text. The job is basic extraction into a structured output. One change is included within 15 days. Larger changes after that are quoted separately.

Standard: Rs 35,000 to Rs 50,000

Rough fit for 5 to 7 formats and about 30 to 35 fields. Same input types as Starter, plus OCR support where scan quality allows, and multiline data. The work usually includes extraction, correlation with your master data files, exception handling, and basic import-oriented reports. Two changes are included within 2 months.

Custom: scoped individually

As many formats and fields as your process needs, including custom file types. Everything in Standard, plus validation reports and advanced custom requirement consultations. Three changes are included within 3 months. There is no fixed price published for this tier. Talk to us and we scope it.

OCR support for scanned documents where the scan quality allows. Clear text-based PDFs always give the most dependable results; poor scans may need a cleaner copy.

The five cost factors behind the quote

Even inside a tier, two jobs are not equal. We itemize so you can see where the hours go. The same factor list shows up when we talk about custom automation in general, but here it is specific to PDF and Excel document workflows.

1. Document formats and templates

One stable vendor layout is cheap to encode. Nine layouts across seven vendors is a different project. Variation inside a "family" still counts: a small label drift can be normalised; a new table structure usually cannot.

2. Fields to extract

Straightforward single-line values are one kind of work. Multiline blocks, addresses that must be split, and values that only make sense when cross-referenced to another field take longer to specify and test.

3. Validation and reconciliation

No validation means you mostly trust the printed values. Master-data lookups, calculations, cross-field checks, and dispute flagging are where a lot of operational value lives, and where scope grows. A bill checked against a purchase order and an Excel line list is not the same job as "dump fields to CSV."

4. Reports and output files

A simple structured file is one deliverable. Highly formatted analytical workbooks or elaborate layouts are another. Import-ready shapes for a specific accounting import are usually closer to the first, unless the import schema itself is awkward.

5. Other implementation needs

Anything specific to your process that sits outside the items above: packaging, deployment habits, odd folder watching, or consultation time on edge cases. We list those lines instead of burying them in a round number.

Simple versus complex, in plain examples

• Single layout versus many layouts from different senders
• Plain fields versus multiline or cross-referenced values
• No validation versus master lookups and reconciliation
• Simple CSV versus a formatted analytical report

Move right on those axes and you move up a tier, or deeper into Custom. Move left and Starter may be enough.

Payment and licence

Larger projects are paid in phases, after each segment of the work has been delivered. Small jobs are paid on delivery. Until payment is made, the software runs on a temporary licence. Once payment is complete and the licence is unlocked, it works for life.

The agreed software delivery does not require a mandatory recurring subscription. Paid support and separately agreed future work may incur additional charges. We do not publish support-plan prices here. Post-sales support is part of how we work; routine runs are built so you rarely need day-to-day developer help.

We do not claim refunds, free trials, or guarantees that are not written into your quote.

A rule of thumb on payback

In our experience, an automation like this typically pays for itself once about 500 to 700 documents have been processed end to end; beyond that, the savings and the fewer errors are a bonus. That is a rule of thumb, not a guarantee, and it is not attached to a specific client or tier.

Separately, the Workflow Automation application's own About screen has shown figures such as 317 files and 42 reports in 5 minutes, with the application's own estimate of 27 hours 2 minutes if done manually. Treat that as an estimate from the software's counters, not a promise for your mix of documents.

How a delivered project was itemized (generic)

One real delivery was broken into separate lines such as: a bulk PDF upload and processing dashboard; custom field-extraction templates; an integration that pushes processed data into the customer's accounting software through its API; cross-source extraction that combined PDF fields with master data from an external file; and optional yearly support. That structure is what "itemized" means in practice. You see the pieces. You can challenge a line. You are not staring at a single opaque lump sum.

In that delivery, seven vendors and nine PDF formats were handled with curated, per-template logic. Support was quoted because the client wanted a vendor who would still answer after go-live. Routine runs were still designed so they would rarely need that help. We do not publish the support figure here.

What we do not compete on

We do not compete on price per page against cloud extractors. We compete on the total outcome: checked data, an exceptions list, and outputs ready for the next step, running on your Windows PC by default.

FAQ

Can you give a firm number on a call with no files?

We can point at a tier. The itemized quote waits for samples.

Are the tier prices inclusive of every tax?

We do not discuss taxes next to these ranges on the site. The quote will state commercial terms clearly.

What if we need a new format six months later?

That is new scope. Recurring template issues on formats already delivered are handled as support; major logic changes or new formats are quoted separately.