Development guide
A few clear notes can make the conversation much more useful. You do not need a polished pitch deck or a finished specification.
Before we talk
Use these prompts to organize what you know and the questions you need to resolve.
Explain who will use the product, what they need to accomplish, and how they handle that task today. A concrete example is more useful than a long feature list.
Gather any sketches, CAD, photos, prototype videos, schematics, test results, or supplier feedback you already have. Note what works, what fails, and what has not been tested. An early idea is a valid starting point; bring what exists.
You may need to establish feasibility, solve a technical problem, build a demonstration, or prepare for manufacturing. Identify the next decision and what evidence would help you make it.
Share the budget range available for the next stage and any important dates. Explain what drives each deadline, such as a customer demonstration, funding milestone, or production need. If you do not know the budget yet, say so.
Include known requirements for size, power, operating conditions, connectivity, target cost, or production quantity. Mention safety, certification, grant, or institutional requirements that may affect the work. Unknowns are useful to identify too.
Write down the questions you want to cover. Consider including the person who understands the technical work and anyone responsible for scope or budget decisions. Be clear about which decisions you can make and which need further review.
A simple starting brief
Copy this outline into your notes and replace the brackets with your project details. Rough notes are a useful starting point.
Project brief
We are building [product] for [user] to solve [problem].
We currently have [existing work].
We need help with [next decision or technical challenge].
Our target is [milestone] by [date], with a budget range of [range or not yet established].
For the initial inquiry, a high-level description is enough. Before sharing confidential files or restricted research, flag any disclosure requirements so an appropriate sharing arrangement can be agreed.
Keep these notes for the conversation and wait for a reply from AVA Labs. Submitting the form does not book a call; there is no need to submit it again.
Before your first development call with AVA Labs, there are five things we'd like you to prepare.
First, be completely transparent.
Think of this like visiting your doctor. We're here to help, not judge you.
If a previous prototype failed, your engineering team is struggling, or mistakes have been made, tell us.
We've encountered all kinds of engineering problems. Hiding information only makes it harder to help.
Second, understand your budget and be honest about it.
Know how much money you realistically have available for development.
Don't hide your budget or inflate it to appear better funded than you actually are.
Understanding your financial circumstances allows us to recommend an appropriate scope of work.
You should also have a credible plan for financing development and eventually bringing your product to market, whether through outside investment, personal funding, or another realistic financial strategy.
Ideally, you should already have a clear go-to-market strategy.
Building a prototype is only one part of creating a successful business.
Third, use tools like ChatGPT or Claude to organize your thoughts.
These tools can help turn scattered ideas, conversations, and documents into something easier to review.
Just be mindful of confidential information when uploading files.
Fourth, send us all relevant documentation before the meeting.
CAD files, photographs, diagrams, videos, previous prototypes, and test results are all helpful.
Even napkin sketches, voice recordings, and rough notes are perfectly acceptable.
Nothing needs to look professional. We'd rather receive more information than discover later that something important was missing.
Fifth, send your major technical questions in advance.
Complex engineering problems require time to investigate.
Introducing difficult technical questions during a meeting and expecting immediate answers is rarely productive.
We prefer to review the information, consider alternatives, and provide thoughtful engineering guidance rather than speculate on the spot.
The goal of your first meeting isn't to impress us. It's to give AVA Labs an accurate understanding of your project, your financial circumstances, and what you're trying to accomplish so we can recommend a realistic path forward.
Your next step
Use your notes to tell AVA Labs where the project stands and what needs to happen next.