Start with a defined outcome
Service bundles with a scope you can evaluate
Use these starting scopes to brief your team and request a written quotation. They describe the work to agree, not fixed-price packages or promises that every integration and service is included in a software subscription.
What every quotation should make explicit
- Named document collection or process, users, volumes and environment.
- Deliverables, customer inputs, acceptance tests and responsibilities.
- One-time implementation charges, recurring software/support, applicable taxes and payment terms.
- Milestones, assumptions, exclusions and the process for approving additional work.
Digitize & Find
For a team that needs an agreed collection of paper or digital records to become searchable and accessible to the right people.
| Scope area | Starting point to confirm |
|---|---|
| Included deliverables | Collection inventory, sample capture/OCR plan, index-field design, role-based retrieval setup and handover. |
| Define before quoting | Record types, page/file volumes, condition, source locations, required fields and user roles. |
| Acceptance | Reconcile imported files against a manifest; check sample quality, metadata and retrieval by authorized roles. |
| Separate or excluded work | Unspecified historic archives, extensive data repair, hardware, disposal, ERP development and additional collections. |
Finance Approvals
For a finance or accounts-payable team starting with one defined invoice approval process.
| Scope area | Starting point to confirm |
|---|---|
| Included deliverables | Process map, agreed capture/index fields, approval routing, return-for-correction path, user training and handover. |
| Define before quoting | Invoice volume, approval levels, delegation, document matching, system interfaces and business owner. |
| Acceptance | Demonstrate the agreed normal, returned, delegated and exception cases using approved sample documents. |
| Separate or excluded work | Unspecified accounting/ERP development, tax advice, unlimited workflows, historical backlog and product add-ons not in the quote. |
Enterprise Governance
For a department that needs controlled document access, revisions and accountable handover.
| Scope area | Starting point to confirm |
|---|---|
| Included deliverables | One agreed document family or process, access matrix, metadata/version design, review responsibilities and an administrator handover. |
| Define before quoting | Owners, document versions, approval roles, security requirements, integrations and reporting expectations. |
| Acceptance | Demonstrate authorized retrieval, restricted access, the agreed revision/approval route and available audit evidence. |
| Separate or excluded work | Organization-wide policy rewriting, certification, legal opinions, unscoped integrations and unlimited administration. |
Government Records Planning
For an agency or LGU that needs a documented starting point before selecting or expanding a records system.
| Scope area | Starting point to confirm |
|---|---|
| Included deliverables | Planning sessions for one agreed office or collection, inventory outline, draft access matrix, gap register and phased pilot plan. |
| Customer decisions and inputs | Records officer and DPO participation, existing schedules, sample inventory, system constraints and acceptance owners. |
| Acceptance | Walk through the inventory fields, unresolved decisions, pilot scope, responsibilities and proposed evaluation checks. |
| Separate or excluded work | Official schedule approval, legal advice, disposal authorization or execution, procurement award decisions and a full archive migration. |
Bring enough detail to make the first conversation useful
Tell us the department, process, approximate volume, existing systems and the problem you want to resolve. Describe the records without sending personal data or confidential document samples through the inquiry form. We can agree a suitable way to review samples during scoping.