Avoice

Lunch & Learn

We bring lunch to your office and run a live Avoice demo for your whole team, on a project like the ones you work on.

  • Lunch for the whole team, on us
  • Live demo on a project like yours
  • About an hour, so it fits a lunch break
  • In person at UK offices

What to expect

One hour, one live demo, everyone fed.

  1. Before

    Tell us what you work on

    We pick a demo project close to your building type, discipline and stage.

  2. 12:30

    We arrive with lunch

    Set up on your meeting room screen in ten minutes.

  3. 12:45

    Live demo

    Spec writing, schedules and a QA check on a project like yours, start to finish.

  4. 13:20

    Questions and hands-on

    Your team tries it and asks anything.

  5. After

    A trial if it fits

    If the team wants to carry on, we set up a trial workspace for the practice.

Questions

Before you book

I like it, but I'm struggling to get my head around it. Where do I start?

That's how most people feel at first, and it's completely normal. Avoice changes how a spec gets written, not just how fast, so it takes a little time to click.

Just send us an email at hello@avoice.co. We'll book a session and start with one section on one of your live projects, ideally something you know well, like internal partitions or floor finishes. We'll go through it slowly with you: how the draft was written, where each clause came from, what's still open, and how you'd review and edit it.

Between sessions, a few things help it sink in:

Ask the spec questions. Why did it choose that value? Where did that clause come from? What's still to decide? Seeing how it answers is the quickest way to understand how it works.
Check something you've already issued. Run a spec you know inside out through Avoice and see what it finds.
Use AI for small things every day. The more you use it, even for simple questions, the more natural it becomes.

At the end of the day, though, none of it will fully make sense until you try it yourself.

I tried AI before and it was inaccurate. Why would this be different?

That's a fair experience to have. AI can get things wrong, and anyone who tells you otherwise isn't being straight with you. Before deciding it can't be trusted, it's worth asking a few questions about how it was tested.

1. When did you last try it? If it was when ChatGPT first came out, or even a year ago, you were using a very different tool. AI models are improving in months, not years. We're used to software that changes a little every year or so. AI changes in weeks, and that takes some getting used to.

2. Which plan and which model? With most software, the free version is the paid version with fewer features. With AI, they can be completely different. Even within one provider such as Claude, ChatGPT or Gemini, the smaller, cheaper models and the most capable ones give very different answers to the same hard question.

3. How was it set up? A general chatbot answering from memory is not the same as AI given your drawings, the regulations and your office master, with tools built to check its own work. Most of what makes AI reliable for specifications is in that setup, not in the model alone.

4. Who ran the test? This one is worth asking gently, because it applies to all of us. Getting good results from AI is a skill, and like any skill it takes time to learn. The same tool can look unreliable to someone trying it for the first time and transform the work of someone who uses it every day. The difference is usually in how it was asked, what it was given to work from, and whether its answers were checked against its sources.

Architects and engineers know this feeling from the other side. Most have had a client, a neighbour or a relative look at a drawing and say the building will fall down, or that the design is wrong. The concern may be sincere, but it isn't the same as a structural engineer's judgement, and nobody would change a design on the strength of it. A judgement about AI works the same way. It carries most weight when it comes from someone who has spent real time with the tools.

So it's fair to ask: did the person who tested it use AI regularly? Did they choose the right model, give it the right information, and know how to push back when an answer looked wrong? If not, the test may say more about the setup than about the AI. None of this means the concerns were wrong. It means the test is worth running again with someone experienced, and we're happy to be that someone on one of your own projects.

The quickest way to settle it is to try it yourself. Even before you look at Avoice, take out a paid plan with one of the main providers, usually around £20 a month, choose its most capable model, and ask it something difficult from your own work.

Technical directors are paid to be cautious, and that's a good thing. Test thoroughly and look at every option. Just don't judge today's AI by what it could do a year ago, or by how quickly other technology has changed in the past. Nothing has moved this fast before.

Before you decideChecklist
Tried it in the last few months
Not when it first came out, or a year ago
Used a paid plan and its most capable model
ChatGPT, Claude or Gemini, usually around £20 a month
Gave it the right information and tools
Your documents and sources, not a chatbot answering from memory
Had someone experienced run the test
Or ask us to run it with you on one of your own projects
I'm philosophically against AI writing specifications. Why would I use this?

You don't have to change your view to test it. Treat Avoice like a new graduate whose work you haven't seen yet. Give it one live project, review its draft the way you would theirs, and keep your current process running alongside.

Better still, turn your objections into the test. Decide up front what would convince you: source accuracy against your own spot-checks, whether it missed anything your master would have caught, and how long the review took. If it fails, you've lost nothing.

If you'd rather not let it write anything yet, start with checking instead. Run a spec you've already issued through Avoice and see what it finds.

More questions

Prefer email? hello@avoice.co

Prefer to book directly? Open the booking form