Short answers to what agencies actually ask us before the first call. If yours is not here, write to hello@ayaner.com and we will answer it, then add it to this page.
Working with us
Who is Ayaner for?
WordPress agencies and product teams in the United States and the United Kingdom that need engineering capacity they can hand a spec to. Most of our work arrives from a technical lead who is out of build hours, not from an end client. We also sell our own plugins directly, and those are for anyone running WordPress.
Do you work white label?
Yes, and it is the most common arrangement. We ship under your name, we do not contact your client, and we do not put the work in a portfolio without written permission. Where you want it, we work inside your repository, your ticket tracker and your coding standard rather than ours.
What time zone are you in?
We are in Istanbul, UTC+3. That is 5 hours ahead of New York and 2 ahead of London, so a brief sent at the end of your day is usually answered before your next one starts. We keep a fixed overlap window with every retainer client.
How do engagements start?
A 30 minute call, then a written statement of work with scope, deliverables, dates and price. Nothing is built before that document is agreed. For a first project, most agencies start with a fixed scope piece rather than a retainer, and we prefer it that way too.
What does it cost?
Fixed scope work runs from around 450 US dollars for a performance pass to several thousand for a full plugin build. Retainers are monthly capacity, quoted after we have seen the work. Every solution page on this site carries its own price band, and none of them are a starting point that quietly triples.
Do you sign an NDA?
Yes. Send yours and we sign it, usually the same day. If you do not have one, we have a mutual NDA we can send instead.
Code and delivery
Who owns the code you write for us?
You do, once it is paid for in full. We keep our pre existing libraries and tooling, and you get a perpetual licence to use them inside the deliverable. This is written into every statement of work rather than left to be argued about later.
What standard do you build to?
WordPress Coding Standards, PHP 8.1 and above, no direct database calls where an API exists, translation ready strings, escaped output, nonces on every state changing request. We write the readme and the inline comments a maintainer needs, because the person maintaining it will usually be you, not us.
Do you do Gutenberg blocks or classic PHP?
Both. Native blocks in React where the client edits content, classic PHP and Elementor widgets where the site already lives there. We ask what the editor is actually using before choosing, rather than defaulting to whichever is newer.
Will you take over a plugin somebody else wrote?
Yes. That is the Plugin Maintenance and Rescue engagement: an audit first, in writing, saying what is wrong and what it will cost to fix, so you can decide whether to repair or rebuild. Around a third of those audits end with us recommending a rebuild, and we say so even though the repair is the easier sale.
What happens after handover?
Thirty days of warranty on anything we built, covering defects in our own code at no charge. After that, support is either a retainer or hourly, whichever suits the volume.
Plugins we sell
What does a licence include?
Twelve months of updates and email support, for the number of sites the licence covers. When it expires the plugin keeps working; only updates and support stop. Full detail is in the Terms of Use.
Can I use them on client sites?
Yes, within the site count your licence covers. What you cannot do is resell the plugin as your own product or publish the licence key. See section 3 of the terms.
Are they GPL?
The PHP is, because it inherits the GPL from WordPress, and we do not pretend otherwise. What you pay for is the distribution: updates, the licence key and support.
Is there a refund if it does not fit?
Fourteen days, in full. We ask to try a fix first, because most refund requests turn out to be a plugin conflict we can solve in a day, but the decision stays yours. See the Refund Policy.
Do the plugins phone home?
Only for licence validation and update checks, and only the licence key, the site URL and the plugin version. No visitor data, no content, no analytics. Everything they send is listed in the Privacy Policy.
AI search and GEO
What is GEO, and is it different from SEO?
Generative engine optimisation is the work that makes an AI assistant able to quote your page accurately. Classic SEO competes for a ranked position on a results page. GEO competes to be the source an answer is built from, which rewards different things: unambiguous entity markup, one canonical page per topic, claims that can be checked, and content structured so a passage can be lifted without losing its meaning. The two overlap, but optimising for one does not automatically deliver the other.
Can you guarantee ChatGPT will cite us?
No, and be careful with anyone who does. Model providers do not expose a ranking API, retrieval changes between model versions, and there is no placement to buy. What we can do is fix the reasons a model currently cannot use your site, then measure how often it does before and after.
What is in the free analysis?
An automated report on your site’s technical GEO and SEO signals: schema coverage, entity clarity, crawlability, Core Web Vitals, heading structure and content depth, each scored with the specific fix. It is generated from public signals only. Nothing is installed on your site and no credentials are needed.
Is the free analysis really free?
Yes. No card, no trial that starts billing. We ask for an email so we can send the report, and you can unsubscribe from anything else in one click.