Frequently asked questions
Useful answers before you get in touch.
Find out how requirements are assessed, how delivery is agreed and what is—and is not—included by default.
Ask a questionGetting started
From an early requirement to a sensible next step.
Do I need a complete technical specification?
No. You can begin with the outcome, users, current situation and known constraints. If important requirements are still unclear, a discovery stage may be proposed before wider delivery work is estimated.
Can you work with an existing system?
Potentially. We first need to assess the available access, documentation, maintainability, dependencies and requested change. Work is confirmed only after the existing setup and proposed scope have been reviewed.
How do I know which service I need?
Start with the problem rather than a service name. A requirement may sit within software development, DevOps or a combination of both. We can discuss the most appropriate starting point after reviewing your enquiry.
Which technologies and cloud providers do you use?
The proposed technology depends on the project, existing systems, security requirements and long-term needs. We do not recommend a specific tool or provider before understanding that context.
Scope and delivery
Make timing, cost and change clear.
How long will the work take?
Timing depends on scope, complexity, access to existing systems, dependencies and how quickly decisions or feedback are provided. An estimated schedule is supplied after the requirement has been reviewed.
How is the work priced?
Pricing is based on the proposed scope and delivery approach. Where the requirement is still uncertain, a separate discovery stage may be suggested before a wider estimate is prepared.
What happens if the requirement changes?
We discuss how the requested change may affect scope, timing and cost before proceeding. A material change is documented rather than assumed to be included automatically.
Do you work in stages?
Where appropriate, work is divided into manageable stages with agreed review points. The actual delivery and acceptance approach is set out for the specific engagement.
Support and assurance
Know the boundaries before work begins.
Do you offer ongoing support?
Support or maintenance may be available by separate agreement. Scope, availability, priorities, responsibilities and any response arrangements must be set out in writing before they can be relied upon.
Do you provide emergency or round-the-clock support?
Not by default. The website does not promise continuous monitoring, immediate response or out-of-hours cover. Any such arrangement would need to be expressly agreed in writing.
Can you guarantee zero downtime or a particular business result?
No. Technical and business outcomes depend on factors including the existing system, architecture, third-party providers, user decisions and operating model. Any specific service target must be defined in the written agreement.
Can you sign a confidentiality agreement?
Hazel Tech can review a reasonable confidentiality agreement before sensitive project information is shared. Please do not send passwords, access credentials or other sensitive values through the website forms.
Have a different question? Contact Hazel Tech
Have something to build or improve?
Let’s turn it into a clear next step.
Tell us what you are trying to achieve. We will review your enquiry and contact you to discuss whether Hazel Tech is a suitable fit.