Ask Yondexy about a website search service, indexing, place data or a company listing inquiry. We are a small digital studio in Austin, Texas. Tell us what the records contain and what you need people to do with them.
No checkout here. Service pricing depends on the records, fields and behaviours in the requested scope. Sending a message does not buy a listing or commit you to a project.
Name and inquiry consent are required. Add either an email address or a phone number so we can reply; you do not have to provide both. The other fields help explain the work.
Brief notes / Before submission
A useful scope names the record, not just the screen.
For a website search service, “make search better” leaves the important decision open: better at finding which information? Start with a task someone needs to complete.
A site search setup inquiry can describe a query that should return a particular record and a filter that should narrow the result. You do not need to design the interface first. For a website indexing service, the equivalent starting point is a source set and the fields it contains. Tell us where updates originate and whether records already have stable identifiers.
Illustrative inquiry interface. A short description is enough to begin.Scope, not access
Send the outline first.
A first message is not a data handover. Explain the format and approximate size of a source instead of pasting a full export. If the work involves information about other people, keep it out of the inquiry.
For place data, distinguish a place label from a coordinate or relationship. For a company listing inquiry, say whether you need a new reference record or a correction to an existing field. Neither request purchases a review score or an external search position.
Company entries, reference fields and update instructions. Define one entry or a batch, and indicate who can supply corrections.
These are scoping bases, not a tariff. Yondexy does not publish a fixed rate in this form. If you used the planning budget estimator, include its assumptions only if you want them considered in the discussion. Its arithmetic uses your figures; it does not calculate a service price.
After sending
Receipt is not project acceptance.
Keep the inquiry reference.
A successful submission returns an inquiry number. Keep it for follow-up. An error message is not a receipt; correct the indicated field or use email if you cannot complete the form.
Clarify the boundaries.
The next discussion concerns the source you can provide and what falls inside the work. Missing fields, uncertain permissions or an undefined update process need to be resolved before implementation is scoped.
Agree the work separately.
A form submission is not a binding quote, a reserved start date or permission to access a private system. Scope and commercial terms need a separate agreement. This page does not promise a service reply time.
Keep changes in the same thread.
If a record count or source changes, send the revision with the inquiry number. State what changed rather than submitting the whole request again with a different description.
Fit and limitsBefore commitment
Ask for controlled work, not guaranteed rankings.
Search project support here concerns the service scope and the data behind it. Yondexy cannot sell a guaranteed ranking, traffic volume or placement in an external search engine. A catalogue entry is a reference, not an endorsement. If your request depends on one of those promises, this is not the right offer.
For a problem with work already agreed, describe the affected field or behaviour and link the relevant correspondence. The correction and warranty limits explain the distinction between work Yondexy controls and a third-party source. For access, deletion or a copy of inquiry information, use the separate data request route.
If a form control is difficult to use, you can send the scope by email or report the barrier through the accessibility contact route. You do not need to finish the form to ask for help.
