
Case study: Rinqa — the website for an AI voice-agent SaaS
How we designed and built rinqa.com: a bilingual, high-conversion website for a SaaS whose AI agents answer the phone 24/7.
A website that has to sell something people don't know exists yet
When we kicked off the Rinqa project, the challenge wasn't just technical. It was about communication. Rinqa is a SaaS platform that deploys artificial-intelligence agents that answer a business's phone and chat 24/7 — with natural voice, not the old "press 1 for…". The catch: most small businesses don't even know this is possible yet.
The website had to do two things at once: explain a brand-new product category and convert skeptical business owners who have suffered through too many useless chatbots. No pretty brochure without results.
What Rinqa does (what the site has to sell)
Rinqa boils down to one line: "let Rinqa pick up the phone." When a business doesn't answer —lunchtime, after hours, call spikes— it loses customers. Rinqa wins them back:
- A natural voice agent that takes the call, answers questions, and handles bookings or appointments.
- A per-business knowledge base: the agent answers with its real information, not generic data.
- Smart transfer to a human when needed.
- Chat and WhatsApp support on top of voice.
- Full analytics on every call and conversation.
And all of it configurable in minutes, by industry. That was the promise the website had to land in five seconds.
What we built
rinqa.com isn't a single-page landing. It's a complete, bilingual (ES/EN), conversion-focused site from end to end:
- A home with a live demo: visitors can ask the agent to call them instantly, or call a demo number and talk to the AI themselves. You can't sell a voice agent by describing it — you have to let people hear it.
- Industry landing pages: restaurants, real estate, dental clinics, gyms, and more. Each with its own copy, its own objections, its own use cases. Not the same page repainted: each industry sees its own reality.
- An ROI calculator: visitors enter their calls per day, conversion rate, and average ticket, and see how much money they're losing to unanswered calls. The most powerful sales argument is their own number.
- A "human receptionist vs Rinqa" comparison: a page that tackles the most obvious objection head-on.
- A pricing page, blog, about page, and the full legal set (privacy, legal notice, cookies, terms, DPA) — because a SaaS handling customer data needs to build trust from minute zero.
The technical complexity under the hood
This isn't "WordPress with a template." As in any project where professional web development makes the difference, the architecture matters.
Truly bilingual, not half-translated
i18n done right
The whole site runs in Spanish and English with localized routes (/es/... and /en/...), correct hreflang on every page, and per-language translated slugs. Google knows which version to serve each user, and there's no penalizable duplicate content.
Technical SEO from the foundations
The site was designed to rank, not to be patched up afterwards. As we always argue, SEO starts in the design:
- Structured data (JSON-LD) on every page type: organization, FAQ, breadcrumbs, blog articles.
- A dynamic sitemap and
robots.txtgenerated by code — never out of date. - Strong internal linking: each industry links to its relevant articles and vice versa, spreading authority across the whole site instead of hoarding it on the home page.
- Proactive indexing via IndexNow so Google and Bing discover new content in hours, not weeks.
Performance as a requirement, not an extra
Loading speed directly affects conversion and rankings. The site is built on Next.js 16 with server rendering, optimized images, and CDN-served assets. The result: green Core Web Vitals and near-instant loads even on mobile over 4G.
Tech stack
Project stack
- Frontend: Next.js 16 with App Router, TypeScript, Tailwind CSS, shadcn/ui
- Internationalization: custom ES/EN dictionaries with localized routes and slugs
- Product backend: NestJS (multi-tenant,
tenant_idisolation and Row Level Security) - Voice pipeline: Python + Pipecat (Speechmatics ASR → Claude LLM → Cartesia TTS), telephony via Telnyx
- Chat widget: embeddable React on any website
- Payments: Stripe · Data: PostgreSQL + pgvector, Redis
- Deployment: Vercel (web) + dedicated infrastructure for the voice orchestrator
Results
5 min
how long it takes a business to get its AI agent talking, straight from the website
- A complete bilingual website with industry landings, ROI calculator, blog, and live demo.
- 100% technical SEO: structured data, hreflang, dynamic sitemap, and automatic indexing.
- Green Core Web Vitals across every metric, on mobile and desktop.
- A website that doesn't just inform — it lets the customer try the product before talking to anyone.
What we learned
When you sell something the market doesn't know yet, the website can't just describe it. It has to prove it. That's why the key piece of rinqa.com isn't a clever line of copy: it's the button that makes the AI call you and show you.
Projects like Rinqa confirm something we repeat a lot: a good website isn't a display case, it's a conversion machine. It combines clear design, SEO from the foundations, real performance, and —when the product calls for it— an AI assistant that serves your customers for you. If you want to dig into that last part, you might like how an AI assistant works on a website and how it differs from a plain old chatbot.
Got a product that's hard to explain and a website that isn't selling it? Tell us about it — we build websites that prove, not just inform. And if you want to see the result, visit rinqa.com.


