Most website conversations happen in the wrong order. The client asks how much. The agency answers with a build cost. The site gets built. A year later, the invoices start showing up from vendors the client never signed a contract with directly.
Nobody had the second conversation on purpose. It just happens.
Here's what a Vizantir engagement puts on the table up front, and what a typical WordPress agency engagement doesn't.
What a Vizantir engagement discloses
- Build cost, one time, itemized
- Hosting cost per month (Vercel or Cloudflare)
- CMS cost per month (Sanity)
- Domain renewal per year (GoDaddy, NameCheap etc.)
- Optional maintenance retainer (only if the client wants one)
Everything on that list is disclosed before the project starts. Nothing on that list auto-renews on a third-party card without a clear notice. Nothing on that list creates a dependency between the site rendering and someone else's license being active.
If a client wants to cancel the maintenance retainer, the site keeps working. If a client wants to leave Vizantir entirely, the code and content go with them. That's not a favor. That's what the deal was from day one.
What a WordPress agency engagement usually doesn't
Most WordPress builds ship with a stack of premium software the agency picked. The client rarely sees a line item for any of it. The client also rarely finds out how it's licensed until a renewal charge shows up on a card they don't remember giving out.
Common items missing from the up-front conversation:
- The page builder (Elementor Pro, Divi, Bricks, WPBakery) auto-renews annually on the account the agency set up during the build.
- The premium theme has its own annual renewal on its own account.
- The page builder add-on library has its own annual renewal.
- The form plugin, the caching plugin, the backup plugin, and the SEO plugin each have their own annual renewals.
- If the page builder license lapses, the pages built with its widgets stop getting updates. Over time, they stop being compatible with WordPress core and become a security risk.
- If the client decides to leave, the layouts built with the page builder don't export. Only the text does. Everything else is a rebuild.
- If a renewal charge is disputed, the refund policies on most of these products say no refunds on renewals. Support will point the client at the payment processor.
None of that is hidden. It's all in the terms of service, the refund policies, and the plugin documentation. It's just not usually in the conversation when the site is being sold.
Two different definitions of a website
The typical WordPress build treats a website as an ongoing service the client rents from a stack of vendors the agency chose. Every year the site stays online, the client is paying for the right to keep the design rendering. Miss a renewal on the wrong plugin and things start degrading.
A Vizantir build treats a website as a product the client buys. The client pays to have it built. The client pays a small amount to keep it hosted. The client doesn't pay to keep the design rendering, because the design isn't gated behind a license somebody else controls.
Both are legitimate business models. Only one of them is usually explained to the client before the invoice is signed.
The conversation Vizantir wants to have
If you're currently on a WordPress site built by an agency, and you're not sure how many vendors your site depends on, Vizantir will build the actual list against your current setup. What you're paying now, what a custom build would cost, what the three-year and five-year numbers look like side by side.
Sometimes the honest answer is that the current site is fine and switching doesn't make sense yet. Sometimes it's that the renewal stack has quietly outgrown the value it delivers. Either way, the conversation happens before the invoice, not after.