Services / Website development

A website is not a brochure. It has a job to do.

Most sites are judged on how they look and nothing else. We start from what the page has to achieve, whether that is an inquiry, a booking or a sale, and build backwards from there.

Plan your websiteSee what we build

Looking good is the easy half.

Plenty of businesses pay for a site they are happy to look at and quietly disappointed by. The pictures are right, the words are fine, and nothing much happens. Usually it is not the design. It is that nobody decided what the page was supposed to make someone do, or where the inquiry goes once it arrives.

We design the page around the thing it has to achieve.

What we build

Grouped by the kind of site, because what a local service business needs and what a software company needs are not the same thing.

Business and service sites

The site a company is judged by: what you do, who it is for, why you rather than the next one, and an obvious way to start a conversation. Built to be edited by your own team afterwards.

  • Corporate
  • Professional services
  • Local business
  • Multi-location
  • Redesigns
What this involves
  • Structure first: which pages need to exist, what each one has to achieve, and what to cut, all decided before a single screen is designed
  • Messaging: saying what you do in the words a customer would use, not the words your industry uses internally
  • Design and build: on WordPress where you want to edit it yourself, custom-built where editing matters less than behavior
  • Phone first: most visitors arrive on a phone, so the phone layout is designed on purpose rather than squeezed down from the desktop one
  • Yours to edit: your team changes text, images and pages without calling a developer every time
  • Proper handover: a walkthrough recorded, and documentation of how the site is put together

Landing pages

Pages built for one campaign and one action. Matched to the ad or email that sent the visitor, so the message does not change halfway through and lose them.

  • Campaign pages
  • Lead capture
  • Product pages
  • Event pages
  • A/B variants
What this involves
  • Message match: the page repeats the promise of the ad or email that sent the visitor, so nothing feels like a different conversation
  • One action: everything on the page serves a single next step; a second option usually costs you the first
  • The first screen: the offer, the reason to believe it and the action all visible before anyone scrolls
  • Form length: asking only what qualifies the inquiry, because every extra field costs completions
  • Variants: a second version built where it is worth finding out which message works
  • Speed: a slow landing page wastes the click you already paid for

Industry sites

Where a sector needs something standard sites do not do, such as property search and inquiry handling, patient-facing information, booking, course listings, menus and reservations.

  • Real estate
  • Healthcare
  • Hospitality
  • Education
  • SaaS
What this involves
  • Real estate: listings, search and filtering, and inquiries routed per property rather than into one inbox
  • Healthcare: clear service and practitioner information, appointment inquiries, and layouts that work for people who need them to
  • Hospitality: menus, rooms and availability inquiries, handed off to whatever booking system you run
  • Education: courses, intakes, applications and prospectus requests
  • SaaS: explaining the product, structuring pricing, and capturing trials or demos
  • Sector requirements: where an industry has rules about what must appear on a page, we build to them rather than retrofitting

Custom web applications

When a business needs software rather than pages: a portal, a dashboard, a booking system, an internal tool. Built when an off-the-shelf product genuinely does not fit.

  • Portals
  • Dashboards
  • Booking systems
  • Internal tools
  • Member areas
What this involves
  • Scoping: what the software must do, who uses it, and just as important, what it must never do
  • Data model: how information is structured, agreed before anything is built, because this is expensive to change later
  • Build: React and Node where an application is genuinely the right answer rather than a site with extra pages
  • Accounts and permissions: who can see what, and who can change it
  • Admin interface: something your team operates without a developer in the loop
  • Testing and handover: tested against real use, documented, and yours to run

Forms, capture and integrations

The part most sites get wrong. Inquiries that reach the right person, land in the CRM, and set the follow-up going, rather than sitting in an inbox nobody owns.

  • Inquiry forms
  • CRM connection
  • Booking
  • Payments
  • Notifications
What this involves
  • Form design: the fewest fields that still tell you whether an inquiry is worth a call
  • Validation: catching a mistyped email before submission rather than discovering it when the reply bounces
  • Routing: the inquiry reaches a named person or team, not a shared inbox nobody owns
  • CRM connection: written into the system you already use, with the fields mapped properly
  • Notifications: by email, SMS or WhatsApp, so nothing waits on somebody refreshing a page
  • Consent recorded: stored with the inquiry, so follow-up stays inside the permission you were given

Launch, hosting and upkeep

Getting it live properly: speed, search basics, analytics, accessibility, and someone to call when something breaks. Ongoing changes as the business changes.

  • Performance
  • Search basics
  • Analytics
  • Hosting setup
  • Ongoing support
What this involves
  • Speed: image handling, loading order and the things that make a page feel slow before it looks slow
  • Search foundations: titles, descriptions, headings, structure and a sitemap, so pages can actually be found
  • Analytics: Google Analytics set up to answer specific questions rather than fill a dashboard nobody opens
  • Accessibility: keyboard use, color contrast and screen reader basics, checked rather than assumed
  • Hosting: set up with backups and certificates, and documented so you are not locked to us
  • Ongoing changes: the site changes as the business does, and there is someone to call when it breaks

The page is one step, not the whole journey.

A site that captures an inquiry and hands it nowhere has moved the problem rather than solved it.

1

Someone arrives

From search, an ad, social or a recommendation.

2

The page does its job

Says the right thing and asks for one clear action.

3

The inquiry is captured

A form, a booking or a call, with the details you need.

4

It reaches your systems

Into the CRM or inbox the right person actually watches.

5

The follow-up starts

Automatically, so nothing waits on someone being free.

We build the whole of that, not just the first box. If you already have a CRM or a booking tool, we connect to it rather than replacing it.

When we'll tell you not to.

Three things we end up saying often, usually before any quote is written.

You don't need a rebuild

Plenty of sites need a clearer message and a working inquiry path, not a new build. That is a far smaller job, and we will say so.

Don't start with the design

A beautiful page built before anyone decided what it is for tends to get rebuilt within a year. The thinking is cheaper than the rework.

Fewer pages, better

A large site nobody maintains ages badly. Most businesses are better served by a handful of pages that stay accurate.

Sites we have built

Four of them, each with a different job to do. The full write-up on every one is a click away.

Home services, Switzerland · Website and SEO

Pricing a niche installation service before anyone calls

CatDoors

A customer's first three questions, namely can you even do this to my window, what will it cost, and will my landlord allow it, all had to be answered before they would make contact at all.

Read the case study Data and AI consulting, United States · Website and SEO

A consulting site built to carry a service tree that keeps growing

Collectiv

A consultancy selling complex, high-value work to finance and analytics leaders, across a service list that was wide, deep, and changing every quarter.

Read the case study Trades, Seattle area · Website and local SEO

Winning a trade job before the estimator arrives

Peacock Painting

Homeowners choosing a painter are not comparing prices first. They are deciding who they are willing to let into the house for a week.

Read the case study Legal, Maryland · Website build

A signed-off design, built so the firm can grow it themselves

Law Offices of Alex Poberesky

A law firm with a long list of practice areas and a long list of places it serves, which means a page count that only goes up, and a design that had already been approved and had to be built exactly.

Read the case study

All case studies

Questions we get asked

Short answers, and none of them a promise.

How much does a website cost?

Business websites start at $900, and the exact figure comes from a written scope agreed before any work begins. What moves it is how much has to be decided from scratch, how many pages genuinely need to exist, and what the site has to connect to. The strategy, the revisions, the training and the handover are inside the price rather than billed on top of it.

How long does a website take to build?

It depends on scope, and the honest answer is that the thinking takes longer than the building. A straightforward business site moves quickly once the structure and messaging are agreed; a custom application is measured in months. A timeline is given with the scope, not before it.

Do you build on WordPress?

Yes, where the client wants to edit the site themselves, since WordPress hands that control back. Where a project is an application rather than a set of pages, it is built custom on React and Node instead.

Will I be able to update the site myself?

Yes. Sites are built so your team can change text, images and pages without calling a developer, and the handover includes a walkthrough and documentation of how the site is put together.

Can the website connect to the CRM we already use?

Yes. Inquiries can be written into the system you already work from, with the fields mapped properly and the consent recorded alongside them, rather than landing in a shared inbox nobody owns.

The rest of the system

Marketing

Search, paid growth, social and content.

E‑commerce

Shopify and WooCommerce stores.

AI & automation

Assistants, lead handling, workflows.

Starting prices for all of it are on the pricing page, and what goes into every proposal is on our commitment page.

Tell us what the site has to achieve.

Not how many pages. What you want someone to do once they are on it. We'll work out what that takes.

Plan your website
hello@aniverx.com +92 310 4841746 Aniverx LLC, Connecticut, USA

Case study / Home services, Switzerland

Pricing a niche installation service before anyone calls

Aniverx
IndustryHome services, Switzerland
ServiceWebsite and SEO
ClientCatDoors
Websitecatdoor.ch

Project overview

A Swiss company that fits cat doors into glass, doors, panels and walls without replacing the customer's original pane. The service is unusual enough that people did not know whether it was possible for their home, so the website's job was to answer that before asking for anything.

The problem they came with

  • Nobody knew the service existedPeople searching for this do not know the solution has a name. They search for the problem, so a cat, a glass door, a rented flat, which is a very different set of words from the ones a company uses about itself.
  • Three objections before any inquiryIs it possible for my window, what will it cost, and can I do it in a rented flat? Any site that left one of those unanswered was going to lose the inquiry to a competitor or to doing nothing.
  • Four language regions, one countrySwitzerland is not one market. A site in German alone is invisible to a large part of the country, and translation alone does not make a page findable in another language.

What we built

  • A price before any contactA calculator gives an estimate on the page, and the installation prices are published rather than hidden behind a form. Nobody has to speak to anyone to find out whether this is within reach.
  • A photo instead of a site visitThe first step is sending a photo, by WhatsApp or email. It costs the customer thirty seconds and gives the company enough to quote from, so the on-site measurement happens only when the job is real.
  • The renter's objection answered on the pageThe original pane is removed, kept, and can go back when the tenancy ends. That is the sentence that unlocks a large part of this market, so it sits on the page rather than waiting for a phone call.

The results

  • A visitor can find out what the job costs without speaking to anybody.
  • Inquiries arrive with a photo attached, so the first reply can be a real answer rather than a request for more information.
  • The question that used to end the conversation, "I'm renting", is answered before it is asked.
  • The site works in German, French, Italian and English, so the company is reachable across the whole country rather than one part of it.

In short

The site does the qualifying. By the time somebody makes contact they know it is possible, roughly what it costs, and that renting is not a problem, which is a very different conversation to start from.

aniverx.com

Case study / Data and AI consulting, United States

A consulting site built to carry a service tree that keeps growing

Aniverx
IndustryData and AI consulting, United States
ServiceWebsite and SEO
ClientCollectiv

Project overview

A US consultancy helping organizations modernize their data platforms and adopt AI. The buyer is a CFO, an FP&A director or a BI lead doing research over weeks, not a visitor making a quick decision, so the site had to be a reference rather than a brochure.

The problem they came with

  • A service list too wide for one pageStrategy, architecture, implementation, managed services, training, accelerators and migrations, each with their own buyer and their own vocabulary. Flattening that into one services page would have made every one of them invisible.
  • The buyer arrives mid-researchSomebody comparing platforms or planning a migration is not looking for a sales pitch. They are looking for an answer, and they will trust the company that gave it to them.
  • Proof scattered away from the pitchCase studies, partner status and client results existed, but they were not sitting next to the services they proved, which is where they actually do their work.

What we built

  • A page for every real searchEach service, each program and each platform migration gets its own page, so somebody searching for their exact situation lands on a page about it rather than on a general one.
  • Proof placed next to the pitchCase studies, partner recognition and client outcomes sit with the service they belong to instead of in a separate section nobody visits.
  • One way in, on every pageWherever a visitor lands, the next step is the same short conversation request. No maze, no alternative routes competing with each other.

The results

  • Every service has a page that can be found on its own terms, rather than a line on a list.
  • Somebody researching a specific migration lands on a page about that migration.
  • The evidence sits beside the service it supports, where a buyer is already deciding.
  • New services and accelerators can be added to the structure without rebuilding it.

In short

The site was built as a reference for people doing their homework, because that is what this buyer is actually doing when they arrive.

aniverx.com

Case study / Trades, Seattle area

Winning a trade job before the estimator arrives

Aniverx
IndustryTrades, Seattle area
ServiceWebsite and local SEO
ClientPeacock Painting

Project overview

A family-owned painting contractor working across the Seattle Eastside and the wider county. Inquiries come from local search, and the decision is made on trust long before anyone talks about price.

The problem they came with

  • The real objections are never about paintHow many people will be in my house, how long will it take, what happens to my furniture, are you insured, what if it goes wrong. A site that lists services and asks for a phone number answers none of them.
  • Local search is the whole funnelPeople search for a painter in their own town. Being a regional company is no help if the page does not speak about the specific place somebody is typing.
  • Proof that had to be seen, not claimedPainting is judged by eye. Any amount of writing about quality is worth less than one before-and-after photograph of a room like theirs.

What we built

  • The objections answered in the openCrew size, timelines, furniture protection, warranty terms and licensing are written on the site, not held back for the estimator to handle.
  • Built for the towns, not the regionEach service is covered for the places the company actually works, so a search in one of those towns finds a page about that town rather than a county-wide page.
  • Before and after, by job typeInterior, exterior and cabinet work each have their own visible evidence, so a visitor sees the kind of job they are about to ask for.

The results

  • The questions that used to take the first ten minutes of an estimate are answered before the visit.
  • Quote requests arrive saying which job it is, so the estimate can be prepared rather than discovered.
  • The company is findable in the individual towns it serves, not only as a regional name.
  • A homeowner can see work of their own job type before they decide to make contact.

In short

The site does the reassuring, so the estimator arrives at a conversation about the work rather than a conversation about whether to trust the company.

aniverx.com

Case study / Legal, Maryland

A signed-off design, built so the firm can grow it themselves

Aniverx
IndustryLegal, Maryland
ServiceWebsite build
ClientLaw Offices of Alex Poberesky

Project overview

A personal injury and criminal defense firm serving Maryland, Virginia and Washington DC. The design was finished and approved before the build began, and the real requirement was everything that happens after launch: new practice areas, new towns, new articles, all without a developer.

The problem they came with

  • The design was already signed offAn approved design is a promise. Building something that is nearly it is how a client ends up disappointed by a site that is technically finished.
  • The page count only growsPractice areas multiplied by locations is not a fixed number. Hand-building each page would have meant the firm paying a developer every time it wanted to be found somewhere new.
  • One action, from any pageA visitor arriving on a page about one accident type, in one town, at eleven at night, needs the same single obvious next step as everybody else.

What we built

  • Built to the design, not near itThe approved design was built faithfully, so what was signed off is what went live.
  • Templates rather than pagesPractice areas, locations and articles run on templates. The firm fills in the content and the page comes out consistent with the rest of the site.
  • The free case review, everywhereEvery page ends in the same action, so no visitor has to go looking for how to start.

The results

  • The site that went live is the design that was approved.
  • The firm adds practice areas, locations and articles itself, without a developer and without the layout drifting.
  • Every new page is consistent with the ones already there, however many get added.
  • Any page a visitor lands on offers the same single next step.

In short

The build was the easy half. What was really delivered is a site the firm can keep growing for years without coming back for permission.

aniverx.com