Keep the next step clear.
Use the support route agreed for your project. Coverage and response levels depend on your maintenance or support agreement.
Help us understand the issue.
Include the affected system, what you expected, what happened and the steps needed to reproduce the issue.
Use your agreed secure channel for sensitive information. Do not put passwords, private customer records or credentials into a general enquiry.
- Project name and affected environment
- Reproduction steps and relevant timestamps
- Business impact and the people affected
- Screenshots with confidential data removed
Good questions.
Useful answers.
How do we start a project?
Share the problem you want to solve, who will use the software and any constraints. We use discovery to clarify the scope and next steps.
Can you work with an existing system?
We begin with a review of the codebase, documentation and integrations. That review informs whether to improve the current system or plan a replacement.
How are timelines and costs agreed?
They depend on scope, dependencies and delivery milestones. A proposal should explain assumptions, responsibilities and what is included.
Let’s build what’s next.
Bring the challenge. We’ll work through the possibilities.
Discuss your project