The questions we get before anyone signs anything.

The plugins are a subscription, in tiers. Which tier you need depends on how many people need accounts in it and which features you turn on. A hotel with one person taking bookings should not be paying for what a magazine with a dozen contributors and a direct ad desk is paying for.

Moving up a tier is a billing change, not a migration. Nothing is reinstalled and nothing is reconfigured — the features that were closed to you stop being closed.

Custom plugin development is a fixed one-time rate. If we build you something that does not exist yet, you are quoted a fixed price against a written scope, and that is the whole invoice. It is not a subscription and it does not turn into one later.

Ask us for current tier pricing. We would rather quote against the sites you actually run than publish a table that fits nobody.

Nothing on your site gets switched off to make a point. There is no kill switch, no nag screen that takes over the admin, and nothing that disables a page because an invoice went unpaid. What stops is updates, support, and the tiers above the one you were on.

That matters more than it sounds: WordPress and PHP keep moving, and a plugin that stopped getting updates in 2027 will eventually stop working on a 2029 install. But that is your decision to make on your own schedule, not something we force on a renewal date.

The two hub products are the exception, and it is worth being clear about why. The half that runs on your site keeps running; the half we operate stops answering. For ADRS that means your ad zones fall back to your own house creative — the same thing they show when nothing is booked, so zones do not go blank and layouts do not break. For AFX it means the network stops exchanging; if you were also using it to run your own freight, that side of it lives entirely on your server and carries on.

Not a time-limited trial, because two weeks is not long enough to find out whether a booking system fits how you work.

A subscription is a better answer to that question anyway: you can stop. There is also a refund period at the start, no questions asked — install it, run it against real work, and if it is not right, tell us. Ask us for the current terms before you start.

Yes. Everything we sell goes to our sister company, I2 Publishing, for testing before it ships to anybody else — so there is always a live install to look at, carrying real traffic.

Ask and we will walk you through the one closest to your situation, on the real site, with real data in it.

On your site. Upload the plugin, activate it, configure it. Your data stays in your database, on your hosting, under your backups. We do not need access to your server and we do not want it.

Two products are different — ADRS and AFX. Both do something a single site cannot do alone, so both also maintain a separate Intech hub alongside the plugin on your install. In both cases your own records stay in your own database. What the hub holds is only the part that has to be true across more than one site.

Because the thing it sells is exclusivity, and exclusivity cannot be enforced from inside one site.

When an advertiser buys the sidebar on your Mexico section for the month of June, something has to know that slot is gone — and it has to know across every site you run, not just the one the booking was typed into. A plugin sitting on a single WordPress install cannot answer "is this available?" for anything it cannot see.

So the hub holds your sites, your zones and your bookings, and each site's client asks it what to render. That is also what lets one advertiser buy space across three of your publications in a single transaction.

If you only have one site and never intend to have two, say so — a single-site mode with no hub is on the list, and your asking moves it up.

Yours, and only yours. ADRS is not an exchange, not a marketplace, and not a directory of advertisers you pick from. It is nothing like AdSense: there is no pool of third-party demand, and no stranger's creative arrives on your page because an auction cleared somewhere.

What it is, is the system a publication runs its own direct ad sales on — the advertisers you sold, at the rates you set, in the zones you defined, on the sites you own. If another publisher also runs ADRS, you cannot see their advertisers and they cannot see yours, and we cannot sell anything into your inventory.

The writer side works the same way. The contributors in your dashboard are your contributors on your site, and their earnings are calculated from the ad revenue on their own posts on that site. No shared pool of writers, no shared pool of advertisers. The hub coordinates the sites you run; it does not connect you to anybody else's.

AFX is an intermediary network. It connects freight brokers and logistics firms with shippers and carriers, and a network by definition has to reach past the edge of one company's website.

The split is deliberate. Your records stay in your database — your customers, your rates, your equipment, your history. What moves across the network is transactional: the load on offer, the capacity available, the status of something already in motion. Membership is vetted, so the firms you transact with have been approved rather than merely signed up.

And if you do not want a network, you do not have to take one. Used purely to run your own operation — your shippers, your freight, your trucks — AFX is wholly contained within your site, with no hub involved and nothing leaving your server.

Your site carries on as if nothing happened. This was designed for first, before any of the selling logic, because a hub outage that slowed down a publisher's pages would be worse than having no ad system at all.

• The client gives the hub two seconds and no more.
• Decisions are cached, so a healthy hub is contacted once per zone per five minutes, not once per page view.
• After three consecutive failures a circuit breaker opens and the client stops calling for two minutes.

The practical cost of a total hub outage is one slow request per zone per minute, and then nothing at all. Zones show your house creative until the hub is back.

WordPress 6.4 or later and PHP 8.0 or later. No specific host, no specific stack, and nothing that rules out managed WordPress hosting.

If you are running ADRS as a hub yourself — which some publishers prefer — you will also want a real server cron rather than WP-Cron, because bookings go live and expire on dates and WP-Cron only fires when somebody visits the site. The install notes cover it in two lines.

Block themes and classic themes both. We build against WordPress, not against a particular theme.

Placement works two ways. If your theme already declares ad zones, the plugin adopts them and you do nothing. If it does not, you declare them with a short filter and drop a shortcode where you want them — [adrs_zone slug="sidebar-box"] — which works inside any builder that renders shortcodes, which is all of them.

It cleans up after itself. Options, tables and scheduled events go, and your posts and pages are untouched.

One deliberate exception: if you are running an ADRS hub, deleting the plugin does not drop its tables unless you explicitly set a constant in wp-config.php. Advertiser history and the record of what was sold should not vanish because somebody clicked Delete on a plugin screen.

In your database, on your website. Not in an account on our servers that you log into. Not synced to a copy we keep. The plugin creates its tables inside your own WordPress install, and that install sits on your hosting, under your backups, behind your credentials.

If you want to read it, it is SQL. If you want to leave, it leaves with the site. We never hold the only usable copy of anything you depend on.

The two hub products qualify that in one direction only: the hub holds the part that has to be true across several sites — a booking that spans your publications, a load offered to the network — and your own records stay exactly where they were.

Nothing. Not "nothing identifying," not "nothing we would sell" — nothing.

ADRS statistics are a daily count per zone and per placement. That is the whole record. No IP address, no user agent, no session, no cookie, no fingerprint, no third-party pixel. An advertiser is told their creative was shown 4,100 times in June on the Mexico section, and nothing whatsoever about who saw it.

The same rule applies across the range. Subscriber capture, message capture and survey responses store what the person typed and when, and deliberately do not store where they were.

No telemetry, no usage reporting, no "help us improve" opt-out buried in the settings. The only outbound traffic any of these plugins make is the traffic the feature itself requires — the ADRS client asking the hub what to render, and the newsletter handing an issue to your sending service.

Signed, not authenticated with a bearer token. Each request carries an HMAC-SHA256 signature over the site key, a timestamp and a hash of the body, compared in constant time, inside a five-minute window.

The secret itself never travels, and the calls are server to server — nothing reaches a browser, so no key is exposed and no ad blocker sits in the middle of it.

In the other direction, the client runs every piece of markup the hub sends through wp_kses before it goes on the page. Images, links and a short list of wrappers get through; script tags, iframes and event handlers do not. The hub is ours, but a plugin that renders whatever it is handed becomes a cross-site scripting vector into every site it is installed on the moment that hub is compromised.

Nothing in these plugins sets a tracking cookie, so nothing in them is what would trigger a consent requirement. If you already have a banner it is because of something else on your site.

We are not lawyers and this is not legal advice — your obligations depend on where you and your readers are. But we can tell you precisely what the software does and does not store, which is usually what your lawyer actually needs.

Installing it, configuring it, and fixing it when it is wrong. That includes bugs, conflicts with other plugins, breakage after a WordPress or PHP upgrade, and the "it should be doing X and it is doing Y" conversation.

What it does not cover is building you something new. That is custom work, and it is priced as custom work — see below.

Email btdugan@intechcreative.com. One address for every product, so you never have to work out which queue a question belongs in.

We answer during business hours, US Eastern. We would rather tell you our real turnaround when you ask than publish a number that looks good on a page and then gets missed.

The people who wrote it. There is no support tier, no script, and nobody asking you to clear your cache before they read what you sent.

That is most of what we do. Every product on this site started as one client's specific problem that turned out to be everybody's problem.

If what you need sits close to something we already have, you get it faster and cheaper than from scratch, because the availability engine, the reporting and the record structure already exist and are already tested.

Yes, and we would rather do that than rebuild something that works.

We start with a short paid audit — what is there, what is load-bearing, what is going to bite — and you get that written up whether or not you then hire us to do the work. If the honest answer is that the existing code is fine and you need one small thing added, that is what the audit will say.

The default, and the one most studios use: you own the work built specifically for you and can take it anywhere, and we retain the underlying products and libraries it was built on, which you hold on the same subscription terms as any other customer. The exact terms are in the contract, and we walk you through them before you sign anything.

If you need something different — full assignment, or an exclusivity period in your sector — that is a conversation, not a refusal.

Fixed price against a written scope, in stages, with the first stage small enough that you find out how we work before you are committed to much.

We do not quote a day rate before understanding the problem, and we do not quote a project price off a phone call.

A development company, established 2012 in New York, and a service of Inicia Incorporated.

We develop and manage applications that automate what people do manually every day, and we aim deliberately at underserved and fragmented sectors — the markets made of hundreds of small operators rather than a handful of large ones, which is exactly why nobody built for them.

We are not a sprawling company. Our parent is — Inicia Incorporated holds businesses across publishing, media and technology — but the Intech Creative team itself is a small, focused group, and what it is focused on is technology for small business. Nothing else.

What that buys you is that the person who answers your email wrote the code, and a feature request does not have to survive a roadmap committee. What it costs you is that we say no to work we cannot do well, and we will tell you when something is outside what we should be taking on.

It is a fair question to ask any small vendor. We are not a startup — we have been operating since 2012 — and we fully expect to be. But nobody can promise the future, and we are not going to pretend otherwise. What we can do is make the answer matter less.

Everything is standard WordPress — no proprietary runtime, no hosted editor your content lives inside, no format only we can read. Your data is in your database in tables you can query. If we disappeared tomorrow, another developer could pick it up, and the plugins would keep running in the meantime because none of them need us to be alive.

The parts that depend on us are the two hubs — which is why the ADRS client degrades to your own house creative instead of going blank, and why AFX can be run entirely inside your own site if you would rather not depend on a network at all.