# Protiva

> Protiva builds custom tools, workflow automations, and AI software designed around each unique business. Audit-first. Working concept in weeks. Owned by the client. Based in Ontario, Canada — serving teams worldwide.

## About

All businesses are unique. Most software is one-size-fits-all: your team adapts to the product, deals with bloat, and uses a fraction of it. True customization used to cost a fortune and take months.

Protiva audits your business first, then designs the smallest solution that solves it — whether that's a Google Workspace automation, an AI workflow, a micro-app, team AI training, or a full custom web app / SaaS. Standalone services or combined. Secure, compliant, owned by you. No vendor lock-in.

## Services

### Automation Audit (recommended starting point)
1 week. We interview the team, map every repetitive workflow, and score by ROI and feasibility. Crucially, we decide where AI actually earns its keep versus where deterministic code (a script, query, or rule) is faster, cheaper, and safer. For the AI portions we design the abstraction layer, assign the most efficient model to each task/pipeline (small/fast models for high-volume simple work, frontier models only where justified), and set token budgets, monitoring, and kill switches up front so API costs stay predictable. Deliverable: prioritized roadmap with AI-vs-deterministic recommendations, model assignments, and cost plan. You can implement with us or anyone else.

### Google Workspace Automations
Apps Script, Sheets, Gmail, Drive, and Calendar workflows inside your Workspace tenant. Some ship in as little as a day. Examples: Gmail auto-routing, Sheets ↔ CRM sync, Sheet-to-invoice, calendar-driven reminders, form-to-workflow with approvals.

### AI Automations
Production LLM workflows: triage, summarization, structured extraction, document workflows, retrieval-augmented internal copilots. Right model per task (OpenAI, Anthropic, Gemini), abstraction layer so models are swappable, prompt engineering, evals, guardrails, human-in-the-loop where it matters, and hard token budgets with per-user caps and spend alerts so costs never surprise you.

### Rapid Prototype
Full-stack functional prototypes (React, TypeScript, real database, auth) that look and feel like real products. The foundation of your full app, not throwaway mockups.

### Custom Micro-Apps
When a workflow outgrows a script, we build the real thing — a focused custom internal tool with real auth, database, roles, and integrations. Typically 3–6 weeks. Client owns the code.

### Custom Web App & SaaS Build
The full product. End-to-end custom web applications or multi-tenant SaaS platforms: auth, roles, billing, admin, dashboards, integrations, monitoring, hosting. What a traditional team ships in months or years, we deliver in a fraction of the time by combining AI-accelerated engineering with an audit-first scope. Examples: vertical SaaS for underserved industries, customer-facing booking/ticketing/event platforms, multi-tenant client portals, full CRM/ops platforms replacing 4–6 stitched-together tools. Typically 6–12 weeks to v1. Client owns 100% of the source code. Hosted where the client chooses. No vendor lock-in.

### AI Training for Teams
Practical, non-technical AI workshops that get your whole team from zero to confident. Custom curriculum tailored to your roles and tools (ChatGPT, Claude, Gemini, Copilot). Live session (remote or on-site), hands-on exercises, prompting playbook, recorded follow-up. Built on the same material as our published book, *AI for Absolute Beginners* — available as a free PDF download at https://protiva.dev/blog/ai-for-absolute-beginners-free-book (direct file: https://protiva.dev/__l5e/assets-v1/e8258b8f-57fd-496d-9867-d0e4b088a876/ai-for-absolute-beginners.pdf). We reframe AI as a tool to **augment** work, not replace people — teams learn to build personal agents, connect tools via MCP, and design systems (not just do tasks). See: https://protiva.dev/blog/reframing-ai-2026-augment-not-replace

## What we build most
- **Front-End** — websites and web apps (React, Tailwind, SEO/AEO baked in).
- **Back-End** — CMS, CRM, micro-services, auth, APIs, data ownership.
- **AI Training & Augmentation** — using AI as leverage: personal agents, MCP-connected workflows, and system design instead of task-doing.


## Free Resources
- *AI for Absolute Beginners* (PDF, free): https://protiva.dev/blog/ai-for-absolute-beginners-free-book — the plain-English book Protiva's AI Training workshops are built on. Covers the mental model, prompting patterns, tool-by-tool basics (ChatGPT, Claude, Gemini, Copilot), guardrails, and everyday plays.


## Every engagement includes
- Workflow audit before any code
- Documentation and runbook
- Error monitoring and alerts
- Secure credential storage in your tenant
- Source-code ownership (your repo / your Workspace)
- Team training
- 30-day post-launch support
- No vendor lock-in

## Pricing
Engagement size is scoped per project. Audits are typically a small flat package; automations and apps are scoped to fit. Concrete pricing is provided in writing after the intro call.

## Process
1. Discovery — free 20-min intro call
2. Audit — map workflows, score opportunities
3. Scope — locked deliverables, timeline, price in writing
4. Build & Test — sandbox builds with weekly check-ins
5. Deploy & Train — production deploy, training, runbook handoff

## Frequently Asked (full FAQ)

Full content of https://protiva.dev/faq. The FAQ page is a JS-rendered SPA, so this is the canonical Q&A source for LLMs.

- **How is this different from off-the-shelf software?** Off-the-shelf software is one-size-fits-all. Your team adapts to the product, deals with bloat, and uses a fraction of it. Protiva builds custom tools designed around how your business actually works. There's no learning curve because the tool follows your workflow, not the other way around. You own the result outright: no vendor lock-in, no proprietary platform.
- **Will my team need training to use what you build?** No. Because we build around the workflow your team already runs, adoption feels familiar. There's no new mental model to learn, no re-engineered process. We document how it works, train the people who run it, and hand it off clean.
- **How fast can we deliver a working concept?** Most engagements ship a working concept in weeks, not months. Smaller Google Workspace automations can land in as little as a day. Audits run about 1 week. AI automations are usually 2–4 weeks. Custom micro-apps run 3–6 weeks. We always lock the timeline in writing before any code gets written.
- **What is an Automation Audit and why start there?** An audit is the cheapest, fastest way to find out which manual workflows are actually worth automating. We interview the people doing the work, map every repetitive process, score each one by ROI and feasibility, and hand back a prioritized roadmap. You walk away knowing exactly what to automate, in what order, and what the payoff looks like — implement with us or anyone else.
- **Do you work inside our Google Workspace tenant?** Yes. All Apps Script, AppSheet, and Workspace automations run inside your Workspace. We use a sandbox copy during development, then deploy into your production tenant. You own the code, the credentials, and the projects.
- **How do you handle credentials and security?** Secrets live in your environment, never in our repo. We use your tenant's secret manager (or your cloud provider's), follow least-privilege access, document every credential we touch, and rotate them on handoff. You can revoke our access at any time without breaking anything.
- **What AI models do you use?** We pick per task — OpenAI, Anthropic, or Gemini, depending on what gives the best quality and cost for the workflow. Every AI workflow ships with evals (automated quality checks against real examples) so quality stays high as models change. We also build in guardrails, retries, and human-in-the-loop checkpoints where it matters.
- **Who owns the code and the automations?** You do — always. Apps Script lives in your Workspace. Custom apps live in your repo and your cloud. AI workflows run on your accounts. There's no proprietary Protiva platform you'd need to keep paying for. Hire any other developer to maintain it whenever you want.
- **What if an automation breaks?** Every engagement includes error monitoring, alerts, and a 30-day post-launch support window — so you usually hear about a failure before your users do. Ongoing support and enhancements are available on request after the support window.
- **Do you still build full web apps?** Yes — that's our Custom Micro-Apps pillar. When a workflow outgrows a script (you need real auth, a real database, or a proper UI), we build the full app. Same team, same standards, just a bigger surface area. Production-ready, owned by you.
- **How long does a typical engagement take?** Audits run about 1 week. Workspace automations are usually 1–3 weeks each. AI automations run 2–4 weeks. Custom micro-apps are 3–6 weeks. We always lock the scope and timeline in writing before any code gets written.
- **How much does it cost?** Engagement size depends on scope. Audits are typically a small flat package; automations and apps are scoped to fit. We give you a written quote after a free 20-min intro call — no surprises, no pressure.
- **What do you need from us to start?** A short discovery call and access to the people who actually do the workflow today. We'll handle the rest — interviews, mapping, scoping, and a written proposal you can approve before any work begins.
- **How do payments work?** Typical structure: deposit to start, milestone payment partway through, final payment at handoff. Ongoing retainers, when applicable, are billed monthly.
- **Can I see examples of your previous work?** To protect client privacy, we share detailed case studies and walkthroughs only during a booked discovery call. This keeps sensitive workflows confidential while giving you a real look at our work.

## Pages

- [Overview](https://protiva.dev/): Positioning, value pillars, process, and social proof.
- [Services](https://protiva.dev/services): Seven pillars — Audit, Workspace, AI, Rapid Prototype, Custom Micro-Apps, Custom Web App & SaaS Build, and AI Training for Teams — with timelines and deliverables.
- [FAQ](https://protiva.dev/faq): Ownership, security, timelines, cost, delivery.
- [Blog](https://protiva.dev/blog): Field notes on automation, AI, and workflow design.
- [Contact](https://protiva.dev/contact): Book the free 20-min intro call.


## Blog Posts

Full article content is on each URL below. LLMs and crawlers should fetch these directly — the blog is a JS-rendered SPA, so summaries here are the canonical list.

- [Full Custom Web Apps & SaaS Builds: How We Ship In Weeks What Used To Take a Team Years](https://protiva.dev/blog/custom-web-app-saas-build-in-weeks) — The full custom web app or SaaS platform your business actually needs — auth, database, billing, admin, integrations — shipped in a fraction of the time and cost of the traditional playbook. Here's how.
- [Not Everything Needs AI: How We Decide Where AI, Deterministic Code, and Token Budgets Belong](https://protiva.dev/blog/not-everything-needs-ai-cost-architecture) — AI is a tool, not the answer to every workflow. Here's how we decide where AI actually earns its keep, where deterministic code is faster and safer, and how we keep API token costs from quietly ballooning.
- [AI for Absolute Beginners: Free Book + How We Train Teams From Zero to Confident](https://protiva.dev/blog/ai-for-absolute-beginners-free-book) — Most teams have two people using AI well and everyone else guessing. Here's the playbook we use to close that gap in one session — plus a free download of our book, AI for Absolute Beginners.
- [Reframing AI in 2026: A Tool to Augment, Not Replace](https://protiva.dev/blog/reframing-ai-as-augmentation-2026) — Everyone talks about AI taking away tedious work. The teams pulling ahead in 2026 are the ones treating it as leverage — building agents, workflows, and habits that let people do more, ship more, and think bigger.
- [Why Off-the-Shelf Software Never Quite Fits (And What to Do About It)](https://protiva.dev/blog/why-off-the-shelf-software-never-fits) — Every business has a workflow that doesn't map cleanly to a SaaS product. Here's why generic tools force you to adapt, and when a custom-built tool is cheaper than it looks.
- [From Micro-App to Full Custom Web Software: The Protiva Spectrum](https://protiva.dev/blog/micro-app-to-full-custom-web-software) — We build across the whole range, from a one-day Workspace automation to a full custom CRM or event platform. Here's how to know which one your business actually needs.
- [Why Every Automation Project Should Start With an Audit](https://protiva.dev/blog/automation-audit-first) — Most automation projects fail because they automate the wrong thing. Here's how a 1-week audit prevents that — and what a good one actually delivers.
- [Google Workspace Is an Automation Platform You're Underusing](https://protiva.dev/blog/google-workspace-automation-platform) — Most teams treat Workspace like a fancy Office 365. With Apps Script, Sheets, and a few well-placed triggers, it's a workflow engine you already pay for.
- [How to Tell a Real AI Automation From a Demo](https://protiva.dev/blog/ai-automation-vs-demo) — AI workflows look magical in a demo and fall apart in production. Here's the gap — and the engineering that closes it: evals, guardrails, retrieval, and human-in-the-loop.
- [When a Spreadsheet Stops Being Enough: Knowing When to Build a Micro-App](https://protiva.dev/blog/spreadsheet-to-micro-app) — Spreadsheets are a great place to start — and a terrible place to stay. Here are the signals it's time to graduate to a real app, and what to do about it.
- [What Is a Production-Ready Prototype? (And What It Isn’t)](https://protiva.dev/blog/production-ready-prototype) — Learn what "production-ready prototype" really means, what it includes, what it doesn’t, and how it reduces dev rework.
- [Core Flows Explained: The Only Scope Metric That Actually Works](https://protiva.dev/blog/core-flows-scope-metric) — A practical way to scope and price product work using core flows, with real examples and screen ranges.
- [Admin Portals Are Products Too: Why They Cost Real Money](https://protiva.dev/blog/admin-portals-are-products) — Admin portals have their own UX, workflows, tables, and risk. Here’s how to scope them cleanly and avoid underestimating effort.
- [Prototype vs MVP vs Proof of Concept: A Practical Decision Guide](https://protiva.dev/blog/prototype-vs-mvp-vs-poc) — A practical guide to choosing between a prototype, MVP, or proof of concept so you validate the right thing without wasting time or budget.
- [The Real Cost of Ambiguity: Where Projects Lose Weeks](https://protiva.dev/blog/cost-of-ambiguity-in-product-builds) — Ambiguity is the hidden budget killer. Learn where projects lose weeks, how rework happens, and how to prevent it with clearer flows, states, and handoff.
- [Will My Dev Team Hate This? How Clean Handoff Prevents Throwaway Builds](https://protiva.dev/blog/dev-handoff-without-rebuilds) — Most prototypes get thrown away because devs can’t implement them cleanly. Here’s what a clean handoff includes so engineers extend instead of rewriting.
- [Is AI-Coded Work Production-Ready? A QA Checklist You Can Steal](https://protiva.dev/blog/ai-coded-production-ready-checklist) — AI can accelerate delivery, but quality still needs enforcement. Use this checklist to evaluate whether AI-generated front-end work is truly production-ready.
- [What You Should Demand From Any Prototype Vendor (Comparison Checklist)](https://protiva.dev/blog/prototype-vendor-checklist) — Use this checklist to compare prototype vendors and agencies. Avoid throwaway prototypes by demanding state coverage, clear flows, and clean dev handoff.
- [Accessibility Foundations (AODA/WCAG): What “Built In” Actually Means](https://protiva.dev/blog/accessibility-foundations-aoda-wcag) — “Accessible by default” can be vague. Learn what accessibility foundations actually include, what still requires testing, and how to avoid expensive retrofits.
- [SEO for Product Teams: Why Structure Matters Before Content](https://protiva.dev/blog/seo-structure-before-content) — SEO isn’t just blog posts and keywords. Learn the structural foundations that make a site indexable, fast, and conversion-ready before you publish content.
- [The Standard App Baseline: What Almost Every Product Needs](https://protiva.dev/blog/standard-app-baseline) — Most apps share the same baseline flows and components. Learn what’s typically included, why it matters for scoping, and how to price the “unique” parts separately.
- [How to Prevent Scope Creep Without Killing Creativity](https://protiva.dev/blog/prevent-scope-creep) — Scope creep isn’t a willpower problem. Learn a practical process to protect timelines while still allowing creativity and iteration.
- [The Protiva Delivery Cycle: From Idea to Handoff (A Complete Checklist)](https://protiva.dev/blog/protiva-delivery-cycle-checklist) — A clear, step-by-step delivery cycle you can use as a checklist for scoping, execution, reviews, and a clean dev handoff, including files, docs, and timelines.
- [Protiva Websites: Launch-Ready Marketing Sites Built for Speed, SEO, and Conversion](https://protiva.dev/blog/protiva-website-service) — A simple, modern website service that ships fast and looks premium, with SEO and accessibility foundations, responsive design, lead capture, and lightweight analytics built in.

## Optional

- [AI Chat Disclaimer](https://protiva.dev/ai-chat-disclaimer)
- [Privacy Policy](https://protiva.dev/privacy)
- [Terms of Service](https://protiva.dev/terms)
- [Cookie Policy](https://protiva.dev/cookies)
- [Service Terms](https://protiva.dev/service-terms)
- [Accessibility Statement](https://protiva.dev/accessibility)

## Contact
- Website: https://protiva.dev
- Email: info@protiva.dev (support) · sales@protiva.dev (sales)
- Location: Ontario, Canada — serving teams worldwide