Purchasing process

We offer both fixed fee work and day rate work. The processes shown here apply to fixed fee work, although we recommend that you conform to the processes for day rate work also.

Initial estimate

The process that we use to estimate a project fee has these steps:

If you have not already done so, read:
- Documentation project metrics to find out about the duration of typical projects
- Getting information to find out about your team's commitment to the project
- Terms and conditions for software documentation.
If you have not already done so, contact Mike Unwalla, principal of TechScribe, for an informal discussion.
We work in strict commercial confidence. However, if you want to use a non-disclosure agreement (NDA), either use your NDA, or use our NDA.
Download these two checklists. Complete them, and return them to us by e-mail.
- Business requirements checklist. We need to know the business problems that lack of documentation is causing you, and you need to make sure that you have a business case for producing documentation.
- Documentation requirements checklist. This checklist deals with technical requirements.
Optionally, we visit you and your team and discuss the possible solutions to your problem. (If you decide to use our services, we do not charge for this site visit. If you decide not to use our services, we charge for this visit.)
Based on the answers you supply, and assuming that your problem is something we can overcome, we:
- Give you an estimate (an expected lower and upper value) to produce the type of documentation you requested. (Typically, project fees range between about £4,500 and £18,000 plus VAT.)
- Discuss possible alternative solutions.
You commission us to produce a documentation plan.

Documentation plan (project plan)

Typically, a documentation plan takes between three days and ten days (project days, not calendar days) to produce. We produce this for a fixed fee.

You supply:
- A purchase order for the documentation plan
- A copy of your software (or give us access to a web-based system or through a VPN)
- Source materials such as existing documentation, specifications, and marketing brochures.
We use your software to get a general understanding of how it works and of the tasks that users do. (Typically, you give a walk-through.)
We design the structure of the documentation set: what to include, what to exclude, what goes on paper (or in a printable document), and what goes into online documentation. For each deliverable, we specify the structure and the high-level tasks.
We give a fixed-fee quotation (or a set of options) to produce the specified documentation.

RSS feed