Start a project
Share what you have in mind. We will reply with an honest assessment and, where it makes sense, propose a short discovery engagement to turn it into a clear, costed plan.
0% complete
What happens next
After you send your brief
No automated sequence, no sales pipeline. Here is the actual sequence of events.
- 01
We read it properly
Your brief goes to Lyndon directly, not into a queue for a sales team. We aim to reply within two business days, and we will tell you if we need longer.
- 02
You get an honest first view
We say what we think is achievable, what looks harder than it sounds, and what we would question. If AI is not the right tool for your problem - or a much simpler approach would do - we will say so at this point rather than after you have paid for discovery.
- 03
A short discovery engagement, if it makes sense
For anything beyond a small piece of work, we propose a paid discovery phase: mapping the problem, constraints, data and success criteria into a clear, costed plan. You own that plan whether or not you continue with us.
- 04
Build in reviewable increments
Delivery runs in increments with working software you can see early, automated tests, and checkpoints where you can change direction while changes are still cheap.
Before you start
Questions people ask first
What should I include in a project brief?
The problem you are trying to solve matters far more than a feature list. Tell us what is painful or slow today, who is affected, what systems and data are involved, any hard constraints such as regulation or deadlines, and roughly what budget range you are working within. If you do not know some of that yet, send what you have - working out the rest is what discovery is for.
Do I need to know exactly what I want built?
No. Most useful projects start as a problem rather than a specification. If you arrive with a fixed feature list we will still ask what outcome it is meant to produce, because that is where the scope usually needs adjusting.
How much does a project cost?
It depends entirely on scope, and we will not quote a number before we understand the work - a figure invented at this stage would be misleading. What we can do quickly is tell you whether your budget range and your ambitions are in the same neighbourhood, so nobody wastes time.
What if AI is not the right answer for my problem?
Then we will tell you. Genyra works within its licensed activities - AI software design, AI research and consultancy, and AI developing - and a large part of that is judging honestly where a model genuinely helps and where conventional software, a process change, or nothing at all would serve you better.
Who owns the code and the data?
You own the software we build for you, and it is handed over with source code and documentation. We build model-agnostic, interface-isolated systems specifically so you are not locked in to a provider or locked out of your own software. Your data stays yours, and for sensitive or regulated data we can run private, on-premise models on hardware you control.
Is there a commitment in sending a brief?
None. Sending a brief starts a conversation and nothing more. If you would rather talk before writing anything down, book a discovery call instead.