You're pledging to donate if the project hits its minimum goal and gets approved. If not, your funds will be returned.
I am building VAYQ around a simple idea: a person or business should be able to describe the result they need once, instead of manually searching for every separate part of the solution.
Today, even a fairly ordinary task can turn into a long chain of searches, messages, calls and comparisons. You may need a contractor, workers, materials, delivery, equipment or several different companies. Then you still have to compare prices, check who is reliable and coordinate everyone yourself.
VAYQ is being designed to work from the outcome backwards.
If the task is simple, the system may only need to find one suitable person or business. If it is more complex, VAYQ should be able to break the request into separate market tasks and understand what is actually required to complete it.
That may include workers, contractors, suppliers, materials, equipment, transport, logistics or other services.
The important part is that VAYQ should not stop at producing a list of matches. It should help compare qualified options using price, availability, location, reputation, previous outcomes and supporting evidence, and gradually put together a workable path from the original request to a completed result.
For example, a customer might simply say: “I need this construction job completed.”
Instead of separately finding a contractor, workers, materials and delivery, requesting prices from several companies and coordinating everything manually, the idea is that VAYQ should eventually understand the task, break it down, identify what is needed, compare the available options and help assemble a complete solution.
I am starting with simpler use cases in Ukraine because this is where I can test the system first with actual users and practical constraints. But VAYQ itself is being designed for a much broader international market.
Longer term, I expect people and businesses to delegate more of these tasks to AI agents. VAYQ is being designed with that future in mind, so that the same market infrastructure could eventually be used by authorized AI agents acting on behalf of people and companies, including interaction between agents themselves.
VAYQ is still in development. The goal of this stage is to find out whether the core idea works outside the development environment.
I want to answer a few practical questions.
Can someone describe what they need in normal language without first learning how the system works?
Can VAYQ understand the actual outcome behind that request and recognize when important information is missing?
Can the system break a more complicated request into sensible parts, identify the necessary market participants and help compare realistic options?
And most importantly, can the process move beyond recommendations and actually help a task reach a completed outcome?
The first pilot will intentionally be small. I want to start with simpler tasks and a limited group of users and providers in Ukraine.
For example, a small business may need two workers for one day at a specific location and time. Instead of posting the same request in several places and manually reviewing replies, the business should be able to describe the need once and let VAYQ help structure the request, identify suitable candidates and move the task toward completion.
During the pilot I want to see where users get confused, where the system makes poor decisions, what information is missing, how much manual intervention is still required and whether users trust the options the system produces.
I am not trying to produce impressive growth numbers at this stage. I want to find the weak points while the project is still small enough to change them.
If the core proves useful, the next step will be to make the process more repeatable, add more categories of market tasks and gradually prepare VAYQ for broader international use.
The funding would give VAYQ enough runway to move from the current development stage into a controlled market pilot.
One part would go directly into product development: completing the core flows, AI services, hosting, databases, testing, monitoring, security work and the technical infrastructure needed for external users.
Another part is about making the development environment reliable. I am building VAYQ in Ukraine, where power cuts and internet disruptions can interrupt work for hours. I want to set up a capable development workstation, backup power, reliable networking and Starlink so development and testing can continue during outages.
I also expect to use part of the funding for specialist help on an outsourced basis. I am not planning to build a large team at this stage, but some tasks are better handled by people with specific expertise — for example software development, infrastructure, security, UX/UI, testing, legal or privacy work.
Some funding may also cover reasonable operating expenses directly connected to the project, such as workspace or coworking, internet, electricity, communications, software subscriptions, equipment and other basic costs required to keep the development work running.
Another part would support the first pilot: bringing in initial users and providers, onboarding them, testing actual requests, observing what happens and fixing the problems that only appear once people outside the project start using the system.
Some funding will also be needed for basic legal, privacy, accounting and operational work before VAYQ is opened more broadly.
I want to keep the structure small and practical. The goal is not to build a large organization too early. The goal is to give VAYQ enough resources to become stable, reach actual users and learn what really deserves to be built next.
At the moment, I am leading VAYQ myself.
I am responsible for the product direction, architecture, development process and testing. I use AI development tools extensively and bring in specialist help when a task requires expertise I do not have myself.
My background is not in venture-backed software startups. I come from running practical businesses and developing technical products.
For many years I have worked directly with customers, suppliers and contractors and dealt with projects where the final result had to work in practice, not just look convincing in a presentation.
I have not built a market platform like VAYQ before, and I prefer to say that honestly. What I do have is experience taking practical problems, building solutions, testing them in real conditions and changing them when reality shows that something does not work.
That is the same approach I am using with VAYQ: build carefully, test early, use outside expertise where needed and expand only when the core starts proving itself.
The biggest risk is that VAYQ tries to solve too broad a problem before proving one part of it well.
Another risk is that the technology may work while users still prefer the tools and habits they already know. Trust, simplicity and the quality of the options VAYQ produces may matter as much as the technology itself.
There is also a practical risk that decomposition works well for simple tasks but becomes unreliable when a request involves many dependencies, providers or incomplete information.
The longer-term agent-to-agent direction is also uncertain. I believe AI agents will take on more economic tasks, but exactly how that market develops may be different from what I expect today.
That is why I want to test VAYQ while the project is still small.
If the approach does not work, I would rather discover that through a controlled pilot than after building a large organization around the wrong assumptions.
Even a failed pilot should leave useful evidence about how people express demand, where AI-assisted decomposition fails, what creates trust, how supply should be qualified and which parts of the system are worth keeping or rebuilding.
VAYQ has not raised any external funding in the last 12 months. So far, I have been developing the project using my own time and resources.
There are no bids on this project.