Gage Martin

Operations & business systems

Menu

Software that fits the workflow

Make better use of existing settings, connect a handoff, or build the application or website people need to complete a defined task.

The software is in place, but a task still depends on workarounds, retyping or a website that leaves visitors unsure what to do.

Discuss a tool or website

A useful first result

A scoped configuration change, connected handoff, application or website with tested behavior and an operating handover.

Start with a task or visitor journey whose inputs, decisions and intended result can be described.

Does this fit the work?

A good fit when

  • The people doing the work can try representative cases and review the result.
  • Account owners can authorize a bounded configuration, integration, application or website change.

It needs a different starting point when

  • The request requires unrestricted access or changes without a responsible owner.
  • A delivery date or capability is expected before product limits and access can be checked.

A starting scope

Fees
Fees follow an agreed scope.
Starting scope

The starting point is the work you need to do. Keep the software that serves it well, and agree any configuration, integration or replacement before making a change.

A review or focused project can stand on its own. Use this outline to discuss the work; the written proposal sets the agreed scope, commercial terms and acceptance checks.

What you provide
  • The current task, representative examples and the people who use the result.
  • Authorized access, product constraints and the intended release and rollback process.
What you receive
  • An assessment of existing features before proposing new software.
  • The agreed configuration, integration, application or website with source and settings handover.
  • Checks for representative use, failure, recovery and the intended devices.
Outside this starting scope
  • Unapproved account changes, data migration or public launch.
  • Additional workflows or features outside the agreed acceptance criteria.
Access and decisions
  • Account owners approve access and the exact change scope.
  • A named release owner approves any rollout or public publication.
How we check the result
  • The named user completes the agreed task with representative inputs.
  • Failures, duplicate inputs and recovery behave as agreed for that workflow.
  • The operator can maintain the result and use its rollback instructions.
Your involvement
Users explain the task and try the result; account owners provide scoped access and review the release plan.
Ownership and handover
The installation, domain and service accounts stay under your business's control. Handover includes the agreed source and operating instructions.
Planning the work
Product limits, access, scope and review availability determine the agreed schedule.
After delivery
Defects are handled against the original agreement. New features and later upstream changes receive their applicable scope classification before work begins.

Ways to arrange the work

A review you can act on

Follow a defined problem through the people, records and decisions involved. Receive findings, options and a practical next step.

The assessment stands on its own. Your team can carry out the recommendation, or we can scope delivery separately.

A focused project

Deliver a defined change, with agreed inputs, responsibilities, acceptance checks and handover.

Additional sources, features or workflows need a scope decision before work begins.

Care for an agreed system

Maintain a defined installation, investigate findings and keep its operating instructions current.

Coverage and response expectations follow the applicable agreement. Existing care allowances remain in that agreement; this description adds no new allowance.

Planned operational improvement

Work through an agreed backlog of changes and review what happened after people used them.

Capacity, priorities and acceptance are agreed for the work. A recurring arrangement does not include unlimited development.

Related work and its limits