How We Work
Start with the need.
Choose the right approach.
A simple request can move straight to an agreed scope. Larger or less defined projects may need paid discovery first. You do not need a technical brief or a scheduled call to get in touch.
SIMPLE AND CLEARLY DEFINED PROJECTSA direct path to a useful result.
- Explain the need. Describe the task, the difficulty, or what you want to accomplish.
- OPSFix reviews the request. We check fit and ask for any details needed, usually by email.
- Agree on scope, price, and deliverables. Confirm timing, inputs, and how the completed work will be reviewed.
- Complete and deliver the solution. Receive the agreed report, spreadsheet, process document, or tool with the guidance you need.
A small project does not automatically require paid discovery.
COMPLEX OR LARGER PROJECTSA structured path from question to solution.
- Initial inquiry. Explain the need and the intended result.
- Paid discovery, when appropriate. Review workflows, information sources, feasibility, and risks under an agreed discovery scope and fee.
- Project proposal and scope. Agree on deliverables, price, milestones, responsibilities, and acceptance criteria.
- Development or implementation. Build the solution in agreed stages with opportunities to review progress.
- Testing and handoff. Check the result with its users, document essentials, and agree on training and any correction period.
- Optional ongoing support. Arrange recurring reports, maintenance, or improvements if useful.
Paid Operational Discovery
Clarity before
a bigger commitment.
When the problem needs investigation, discovery provides a defined problem, information requirements, source assessment, and a proposed solution with scope and dependencies.
Discovery scope, deliverables, and fee are agreed before that work starts. A subsequent build is a separate decision. An initial inquiry does not commit you to either.
Know what is included.
Each engagement sets out access and data handling, ownership and usage rights, third-party costs where relevant, handoff, and support responsibilities. New requirements are reviewed and agreed before extra work begins.
We plan realistic timelines around the information available. Support has agreed availability and response times; it does not include emergency or 24/7 coverage.
A practical place to start
Tell us what you
need help with.
A short description is enough. No meeting or technical brief required.
Tell us what you need