Custom Agents. Not finding the agent you need? Have one built for your business, and it is not finished until it passes the cases you wrote.
How it worksFour finished applications, each sold once, to one buyer. You receive the source, the schema, the documentation and a bounded handover. You bring the market, the operation and everything that comes after.
Founder Operations
Know What Your Company Is Running.
Property Intelligence
Turn a Property Shortlist Into a Decision.
Travel Intelligence
A Family Trip, With Everyone's Constraints in View.
Group and Business Travel
Group Travel Decisions Beyond the Nightly Rate.
What separates them is not quality. It is who you intend to sell to, which workflows arrive finished, and how much you have to stand up yourself before anybody can use it.
| Application | Intended market | Included workflows | You supply |
|---|---|---|---|
| Mission ControlPrice on Request · Available | Founders and small software operators |
|
|
| Real EstatePrice on Request · Available | Proptech operators and brokerages with a developer |
|
|
| Family TravelPrice on Request · Available | Travel-product founders, agencies and operators |
|
|
| TeamsPrice on Request · Available | Group travel operators and organizations that travel |
|
|
Schema and test counts were measured on 30 October 2026 against the packaged repositories, and a skipped test is never counted as a passing one. Both are re-run against the actual sale commit before a transfer.
An application you cannot run without the people who sold it to you is not an asset. Every handover is the same four things, and a transfer check runs against a clean clone before any of it changes hands.
Six steps, in this order. A request starts a conversation and reserves nothing. Payment and completed transfer are two separate events. The handover has an end date written into it.
The detail page says what the delivered version demonstrates, what you configure, what needs a licence we do not hold, and what is simply not there. Where a demonstration exists it is linked, and it names the version it represents.
A short form: who you are, what you would do with it, and who would set it up. It is a request for a conversation. It is not a reservation, it holds nothing, and it commits neither of us to anything.
The evidence pack with its commit and its verification date, the known limits, the dependency position, and a written scope of exactly what transfers and what VoyantIQ retains. You read all of it before money is discussed, not after.
The asking price is published; an acquisition still ends in an agreement that names the delivered version, the acceptance process, the remedy for an unresolved defect, and the exact scope of exclusivity. Nothing here has been approved by counsel, and contract drafts are not finished.
These are two events, not one. Payment being recorded is not the transfer, and the transfer is not complete until the repository, schema, migrations, configuration and documentation are in your hands and the application comes up from a clean clone on a database you provisioned.
Up to two one-hour sessions within thirty calendar days of delivery, and thirty calendar days to report reproducible defects against the agreed delivered version. After that the relationship ends unless you want a separate one.
