How much does it cost, and how long does it take?+
You’ll have an agreed scope, price and timeline before work begins. Build packages show a starting price, so you can see where to begin. We quote for your specific requirements, including consulting and embedded support.
What do you need from us?+
One person who knows the work and can help shape it, plus relevant examples, data and documentation. A Proof of Concept asks for about three hours of their time; a Working Workflow involves about twelve hours across the team. System access and support from your IT team or developers may also be needed, depending on the scope. Tool licences and usage are separate.
How do we find out whether AI can do the job?+
AI’s capabilities vary by task. A Proof of Concept tests what is possible with your work and material before you commit to a larger build. You get a working test, the findings and a clear recommendation. If the result you want is not achievable with the approach tested, we’ll explain why and whether another approach is worth exploring.
How do we choose the job?+
In the discovery call, together. Good first jobs come up often, have examples to learn from and have a result someone can judge, such as proposals, research briefs and recurring reports.
Does our knowledge need to be organised first?+
No. We organise the material one job needs as part of the build. The rest follows as you add more work.
Is this technical?+
We use the simplest tool that meets the standard, usually one you can already buy. A Proof of Concept runs on documents you hand over, with no access to your systems.
Can we use our existing tools?+
We start with what you already use and check what the workflow needs. Any additional tools or connections form part of the agreed scope.
What do we own?+
Your company knowledge and the methods and workflows we develop for you. We document the setup so you can maintain it, extend it and change partners. Third-party tools keep their own licences and terms.
Who keeps it up to date?+
Your team, with the operating guide we leave. Each build names who owns the knowledge, the instructions and the checks, and how changes are approved. Embedded support can take this on if you want help.
What happens after the first build?+
At handover we recommend the next step: use it as it is, a Working Workflow, a Full Build, or stop. Your team keeps the files either way.
How much can an agent do on its own?+
That depends on the task and the permissions you give it. We agree which steps can run automatically and which actions need a person’s approval.
How do you handle access to our information?+
We identify the information each workflow needs and agree which tools and agents can access it. Access permissions and the chosen providers’ data settings form part of the setup.
What does Zeyra mean?+
Zeyra brings together zero and era: the start of a new age. It reflects our belief that we’re still at the beginning of discovering what people and AI can build together, with plenty of room to shape what comes next.
It also sounds like someone’s name. There’s warmth to it, a little edge, and something slightly unfamiliar. You could imagine meeting someone called Zeyra, or giving that name to an AI you work with every day.
That character suits the company we’re building: curious enough to explore what’s possible, and someone you’d want beside you as you figure it out.