Blueprints

Starting points, not templates.

These are the builds we are set up to deliver well, described as blueprints: what each does, what it is built from, and how long it takes. Every one gets reshaped around your tools, your data and the way your team already works. None of them is a packaged product.

AUTOMATION

Lead to the right rep, in seconds

What it does. A lead from an ad, a form or WhatsApp is enriched, scored and sent to whoever is on duty, with a clean CRM record and a follow-up reminder. No copy-paste, no leads sitting in a sheet.

Built from. Webhooks from Meta, Google and the site, a Python or n8n worker, your CRM's API, WhatsApp Business messaging, a scoring model.

Timeline. 2–3 weeks for one channel; 4–5 weeks for every channel with a dashboard.

AI AGENT

An assistant that knows your SOPs

What it does. Retrieval over your documents, drives and call notes. Answers staff questions with the source attached, and says so when it does not know. Lives in Slack, WhatsApp or a web page.

Built from. A document pipeline, a vector index, an LLM with retrieval and tools, permission-aware access, evaluation sets so answers stay honest.

Timeline. 3–5 weeks including the evaluation set and a tuning round with your team.

WEB

A site your marketers can run

What it does. Fast pages, structured content, forms that land in the CRM with campaign tags. Publishing a campaign page should not need a developer.

Built from. Next.js or Astro, a headless CMS, attribution capture, analytics, Vercel or Cloudflare.

Timeline. 3–5 weeks.

APP

Field app that works offline

What it does. Jobs, photos and signatures captured on site, synced when the signal comes back, with an office admin panel. One codebase for iOS and Android.

Built from. React Native and Expo, local storage and sync, Supabase, push notifications, store publishing.

Timeline. 4–6 weeks to the stores.

DATA

One number everyone agrees on

What it does. Ads, CRM and billing flowing into one warehouse and one dashboard, refreshed on a schedule, so the Monday meeting is about decisions.

Built from. Scheduled extractors, Postgres or BigQuery, dbt models, Metabase or Looker Studio.

Timeline. 2–4 weeks for three sources.

More blueprints

Four more we buildoften enough to have a plan for.

06 — WHATSAPP

WhatsApp AI sales system

What it does. An assistant on your WhatsApp Business number that answers in seconds, asks for company, problem and budget, answers questions from your own material, books a Google Meet or callback into the team calendar, and hands over to a person when it should. Qualified leads are reported back to Meta so the ads improve.

Built from. WhatsApp Business Platform, an AI assistant with your instructions and Q&A, a calendar service, the CRM, conversion events to Meta.

Timeline. 2–4 weeks.

See the service →
07 — FINANCE

Invoice processing without the inbox

What it does. Supplier invoices arrive by email, get read (vendor, tax id, line items, totals), matched to a purchase order, auto-approved within tolerance or sent to an approver with the difference highlighted, then posted to your books and queued for payment.

Built from. Mailbox watcher, document extraction with a vision model, matching rules, an approval step, Tally, Zoho Books or your ERP's API.

Timeline. 3–4 weeks.

08 — SUPPORT

Support triage that answers the easy half

What it does. Every ticket, email or chat is classified by intent and urgency. Questions your documentation already answers get a reply with sources; everything else goes to an agent with context and a draft reply. Time-to-first-reply and tags are logged.

Built from. Helpdesk or inbox integration, a classifier, retrieval over your help centre, escalation rules, reporting.

Timeline. 2–4 weeks.

09 — REPORTING

The weekly report that writes itself

What it does. Numbers pulled from ads, CRM, billing and operations on a schedule, checked for gaps, turned into a short written summary with charts, and sent to WhatsApp, email or Slack every Monday before anyone asks for it.

Built from. Scheduled extractors, a small warehouse, an LLM for the narrative, a template, delivery to your channel.

Timeline. 2–3 weeks.

Why we show blueprints rather than case studies

Client work is confidential, and a number from someone else's business tells you little about yours. A blueprint tells you exactly what we would build, from what, and how long it takes. The numbers that matter are the ones we work out with you in Discover and put in the proposal.

Questions

About the blueprintsand how they become yours.

Is a blueprint a fixed product with a fixed price?

No. It is a pattern we have a plan for. The scope, the integrations and the price are set in Design once we have seen your tools and data.

What if what I need is not on this page?

Most real projects combine two or three of these, or are something adjacent. Describe the workflow in the form below and we will tell you whether it is a fit and what the shape would be.

Do you build with our existing tools or replace them?

With them, wherever they have an API and are not the problem. We replace a tool only when it is the bottleneck, and we say so in Discover with the reasons.

Can we see one of these running?

The live demo on the home page simulates three of them step by step. For a real walkthrough, book a scoping call and we will show how the pieces fit for your case.

Who maintains it after launch?

You can, with the documentation and the accounts in your name, or we do on a monthly retainer. See the Process page for what "ship and own" includes.

Want to know what the manual version costs? Run the numbers.

The calculator puts a yearly figure on any repetitive task from your own inputs, and sends it with your brief.

WhatsApp us