# A proposal workflow, ready for real work.

An example of what to agree before a build. This is a sample, not a client result.

## Worked specimen: one proposal workflow

Synthetic example for evaluating our deliverable format. No customer system was inspected and none of the checks below has been performed.

| Field | Illustrative decision record |
| --- | --- |
| Decision requested | Approve a limited proposal-generation pilot for one operations team. |
| Recommendation | Check the existing CRM template/export first; build only the missing workflow if that option fails the agreed cases. |
| Alternative | Keep the current process while resolving data quality; buying a suitable tool remains an option. |
| Decision-changing test | Can a nominated operator produce a correct proposal from approved data, including a missing-price case? |
| Evidence and state | Not run. The sample shows the check to commission, not a successful result. |
| Budget and approval | Initial build and recurring hosting/support costs must be agreed; no illustrative quote is a customer commitment. |
| Decision owner and date | The client process owner sets the latest useful date and explicitly approves the scope. |

### A buyer response that does not hide a gap

| Field | Illustrative decision record |
| --- | --- |
| Question | Can another customer access our proposals? |
| Truthful specimen response | Not yet verified. Confirm tenant authorization and test direct cross-company requests before asserting the control works. |
| Evidence / owner | No evidence collected in this sample. Client product owner assigns the test and disclosure approval. |
| Gap plan | Run the agreed access cases; quote any remediation separately. Do not claim certification or buyer approval. |

### Three likely changes, with clear responsibility

| Field | Illustrative decision record |
| --- | --- |
| Approved proposal wording | Operator, with appropriate permission and a preview/check. |
| Price calculation rule | Developer or funded support; verify existing calculations and recovery. |
| Different accounting source | New quote after data mapping, access and failure behavior are understood. |

### Expected versus observed

| Check | Expected evidence | Observed state |
| --- | --- | --- |
| Technical acceptance | Valid and invalid records reconcile. | Not run. |
| First use | One nominated operator completes a real case; later repeat use is recorded separately. | Not observed. |
| Recovery | One named failure safely queues retained work; reconciliation and recovery are rehearsed. | Not run. |
| Retirement | The process owner approves stopping one duplicate entry step after validation. | Not authorized; old route stays available. |
| Benefit | Record actual expense ended and new recurring costs for the same period; keep released capacity separate. | Unknown; no savings or sales claim. |


## Less chasing. Clearer decisions.

Send the documents, rough notes or a screen recording you already have. We draft the brief and acceptance checks, keep product context in your repository, and send a short decision digest: recommendation, alternatives, cost, evidence, owner and latest useful decision date. You approve material choices. Complex coordination is scoped separately.

## Test the assumption that could change the investment

Within the agreed Discovery scope, choose one decision-changing uncertainty and a bounded experiment or technical validation. Compare build, buy, repair, reduce and stop. The decision pack records the baseline, result, unresolved risks, initial and recurring costs, essential scope, next investment and acceptance criteria. An inconclusive result stays inconclusive. Recruitment, deep regulatory research and multiple prototypes need separate scope. The existing fee, duration and full build credit stay in the current Discovery offer.

## Help your product through your next enterprise technical review

For a B2B software business with a working product and one identified prospect. This optional fixed-scope module supports your sale after a readiness check: one questionnaire of agreed size, a current architecture and data-flow summary, evidence links, one technical discussion, one revision and a prioritized gap plan. Every agreed question is answered or marked unknown, not implemented or client-owned. You receive a response your team can forward. A known product can be scoped directly; unfamiliar systems need assessment. Remediation, formal audits, certification and legal opinions are separate. Your prospect controls approval and contract signature.

## Finish the replacement: stop the agreed duplicate work

An optional, separately scoped addition for one workflow and one team. Baseline the current steps, data quality, client effort and recurring costs. Agree real cases, a parallel-use period and nominated users; reconcile outputs and exceptions, prepare the archive, and record repeat unassisted use. Keep the old route until dependency, recovery and validation conditions are met, including reconciliation of writes after cutover. Retire only the named steps the process owner authorizes. If retirement is blocked, you receive the evidence, cause and next decision; a blocked retirement is not a completed retirement. Report reclaimed capacity separately from cash expenditure actually ended.

### Useful result

A nominated operator creates a proposal from approved data.

### Proof

Valid and invalid cases reconcile in the agreed version and environment.

### First use

Record assisted completion and later unassisted repeat use separately.

### Independence

The operator changes one template and follows the recovery instructions.

### Old work ends

The owner approves retirement after reconciliation and the recovery window.

## Make ownership something another person can demonstrate

Agree a receiving operator and a small rehearsal: clean setup, staging deployment, restore or export, and one routine change without hidden instructions from the author. List the three likely changes as operator work, supported work or a new quote. Record permissions, baseline skills, results and gaps, then correct the agreed omissions. A prepared Wavect substitute is identified as such; external independence requires an external reviewer. A short exercise can be included in an eligible build; larger onboarding or review is quoted separately.

## Know what happens when the normal route fails

For an agreed critical failure, scope a safe stop, queue, manual path or export, an authorized operator, retained state and an alert owner. Rehearse continuation, reconciliation and recovery in a representative environment; record observed duration, lost or duplicate transactions and remaining limits. Implementation and any repeated exercises require funded scope. This does not add 24/7 coverage or an uptime SLA.

## Get a release recommendation you can act on

Agree the business-journey register, coverage denominator, supported environments, run cadence and change limits. Findings identify version, environment, reproduction, verified business impact, fix owner and remaining risk; duplicates and false alarms are investigated before escalation. The report recommends release, correction or further investigation. The €750/week QA offer keeps its current terms for a supported estate; material setup, application fixes and new features are separately scoped from test maintenance. Local language, payment or device verification can use an agreed specialist, with a bounded matrix and separate quote. A passing suite is evidence for its stated scope.

## A prepared response when a dependency changes

For a qualifying care agreement, assess supportability and stabilization first. Agree a limited register of APIs, versions, certificates, renewals, usage budgets and access dependencies. Each material trigger has impact, options, recommendation, cost, owner and next update; record whether action was executed, declined or blocked. Major upgrades, new spending, production changes and cancellations require agreed authority. Care keeps the system healthy; adoption improvement is a separate funded decision. Coverage follows the signed agreement.

[Discovery](/services/software-discovery/)