Robotics and AI practitioner hours
We work on a named technical problem.
Commission a block of practitioner hours from MazTech. We agree the question to answer and the output you will keep before work starts.
Send us the technical problem
Start with the decision you need to make.
You may have a robot that needs a defined change, a component choice to review or an AI task you want to try with your existing files. Tell us what happens now and what you need to decide next. That gives us a starting point for a piece of work we can describe and quote.
This service is for a project owner or institutional team with a specific question. You can come with code and hardware already in use, or with a proposed experiment. If the request is still broad, we first discuss which part needs attention and what would make the next decision possible.
A test with a clear question
For a prototype, we agree the equipment, conditions and observation the test needs to produce. Describe the behaviour you want to examine and the constraints that matter. The scope sets out what we will try and how the result will be recorded.
A component or system review
Send the proposed specification and the job it must do. We compare the documented details with that requirement and put questions or limitations in writing. A review can end with a reason to change a selection before you buy it.
The proposal names the output.
Practitioner hours are commissioned against a defined piece of work.
A block can end in a prototype, a test report, a repository or a written technical position. We choose the output with you according to the question. A working file needs a different handover from a recommendation about a component.
For development work, the brief should identify the interfaces and existing files. The proposal records which files or documentation you receive and the points you will use to check completion. This keeps the handover tied to the work you commissioned.
Where a question remains unresolved, it belongs in the written result. A test is useful when it tells you what happened under the agreed conditions, including a result that does not support the original idea.
Send the files that explain the starting point.
For robotics work, include the hardware already selected and any drawings or code relevant to the problem. For an AI task, describe the input, the intended output and the tools you currently use. Share enough context for us to understand the job before proposing a scope.
- The behaviour or technical choice you want us to examine.
- The existing equipment, software and relevant specifications.
- The decision you need to make and the deadline behind it.
- The output you need for your own review or project records.
You do not need a finished specification to make an enquiry. A short description can start the conversation. We can then identify the missing details needed to write the proposal.
Tell us who will review the result on your side. Their acceptance points should be part of the brief, especially when the output will be used by someone other than the person arranging the work. A clear handover starts with knowing who needs to use the files or findings.
We agree the time after reading the brief.
A parts review and a prototype require different amounts of work. Send your deadline and tell us which equipment or files are already available. We agree the hours and delivery points around that starting position, with the scope written before the work begins.
If a request changes during the work, the scope needs another discussion. An added interface or a different output changes what must be checked and handed over. Keep your project decision maker involved so the agreed work remains clear.
Send the problem and the decision behind it.
Include the files you already have and when you need the answer. We will discuss the next step with you.