At Vizuh, technology is useful when it keeps the path from a first visit to a confirmed business outcome understandable. We build across acquisition, websites and measurement, so the systems behind a click matter as much as the page it lands on.
Apointoo: connect the click to a confirmed sale
Apointoo keeps a Google Ads click connected to a lead that continues through a form, WhatsApp or a booking flow. When the business confirms a sale, Apointoo can send the outcome and its value back to Google Ads. Its catalog currently contains 22 integration entries: five marked Production, two Beta, one Via API and 14 Planned. These labels describe different stages; Planned connectors are not shipped integrations.
The developer stack includes a TypeScript SDK with Hono handlers and Zod validation. The Apointoo marketing site is built with Next.js 16, React 19 and Tailwind CSS 4. Explore Apointoo.
ClickTrail: keep campaign context available
ClickTrail is the WordPress attribution plugin in the FunnelSheet family. It captures ten advertising click identifiers and preserves them across cached pages, forms and multi-step journeys, including WooCommerce order data. The aim is to help keep campaign context attached long enough to compare acquisition with a later conversion. It does not replace the site’s consent rules or prove the sale by itself.
Explore FunnelSheet and ClickTrail.
B-Hive: a new web experience under review
For B-Hive Living, we are building a new site experience at the /home route alongside the existing rental pages. The site uses Next.js 16, React 19, TypeScript and Tailwind CSS 4; WordPress remains the headless source for its blog and FAQs. The work aims to give the residential brand a clearer web presence while keeping content and measurable lead paths connected.
The /home route is a review preview and is currently marked noindex, nofollow. It is not presented here as a launched public site. View the preview.
One goal across the stack
These projects have different users and interfaces. The shared engineering goal is to preserve useful context, make confirmed outcomes easier to return to the systems that need them, and choose a web stack that teams can maintain. The stack only matters when it helps the whole journey work.