Tell us what you are running
Most people who write to us are already in the middle of something. A Drupal site that needs upgrading before the version reaches end of life. A build that has stalled. A site that works, mostly, where nobody is certain what would happen if it stopped.
You do not need a specification or an approved budget to start a conversation. A few sentences about what you have and what is not working is enough for us to tell you something useful.
Use the form below, email [email protected], or Book a Discovery Call(Opens in a new tab/window)
What to include in your first message
A short message is fine. The more of this you can tell us, the more specific our first reply can be.
- What you are running. Drupal 7, 9, 10 or 11, or something else entirely. The site address on its own is enough for us to work it out.
- Who looks after it now. An in-house team, another agency, a developer who has moved on, or nobody in particular.
- What is prompting the conversation. An end-of-life date, a security review, a redesign, pages that have become slow, or a build that has not landed.
- When it needs to be resolved. An approximate date is useful. Audit dates, grant deadlines and campaign launches all count.
Please keep passwords and access keys out of the message. If we need access later, we will set that up properly.
What happens after you get in touch
Your message goes to Alex Skrypnyk(Opens in a new tab/window), who runs DrevOps. He reads every enquiry and answers it himself. He is also the person who would scope the work and lead it, so the reply comes from someone who has to be right about what he tells you.
Expect an answer the same business day in most cases, and always within 2. We work Australian hours from Melbourne, so a message sent late on Friday is usually answered on Monday.
That first answer is a real one. Depending on what you send, it might be a rough sense of the size of the work, the 2 or 3 things we would want to look at first, or an honest note that this is work somebody else is better placed to do.
What a first conversation looks like
If it is worth a call, we book 30 minutes. We will ask what the site does for your organisation, who depends on it, what has been tried already, and what your constraints are: budget, timing, procurement, an internal team that needs to stay involved.
You will get our read on the situation during that call, including the parts we think carry the most risk. Where there is work to do, we write it down, and you approve the scope and the cost before anything starts.
Who you would be working with
DrevOps is a Melbourne-based digital agency that builds and supports Drupal websites. We work with government, higher education and enterprise teams across Australia, usually on sites their organisations depend on every day.
If you would rather read before you write, our services page covers upgrades, support plans, audits, migrations, automated testing and hosting. The blog is where we write about the work in more detail.