Everything people ask
before they book.
Timelines, pricing, ownership, security, the AI layer, and what happens after launch — answered the way we'd answer them on a call. If yours isn't here, it's a one-line email away.
Nothing matches that — try a shorter word, or just ask us directly.
How fast can we be live?
A Launch build ships in about two weeks and Growth in four to six. Command runs eight to twelve weeks, and Sovereign is phased — with the first systems live inside the first month either way.
What's the first step?
A free 30-minute discovery call. We map your funnel, tell you what we'd build and in what order, and follow up with a fixed-scope, fixed-price proposal. Useful even if you never hire us.
How much of our team's time does a build take?
A kickoff session, a few working sessions during the build, and a named point person for access and decisions — typically two to four hours a week. We do the building; you do the deciding.
Do you work remotely?
Yes — engagements run remote-first, with working sessions recorded and every decision documented. Time zones have never been the hard part of this work.
What size of company do you work with?
The sweet spot is 20–500 people — big enough that leads slip through seams, small enough to move fast. Outside that range, ask; the discovery call will tell us both.
Which industries do you know best?
Recruiting and staffing, B2B SaaS, agencies, and professional services — each has its own page on this site with a sample architecture. The method transfers to any B2B funnel with real deal sizes.
How is pricing structured?
Fixed scope, fixed price, mapped to one of four programs — Launch $25k, Growth $75k, Command $180k, or Sovereign from $350k — agreed in writing before the build starts. No hourly billing, ever.
Are there costs beyond the program fee?
Only the subscriptions for tools that run in your own accounts (CRM, automation platform, AI usage) — billed to you directly at cost, listed transparently in the proposal. We take no margin on tools.
Who owns what gets built?
You do, from day one. Accounts, automations, prompts, dashboards, and documentation are set up in your name and handed over with SOPs.
What are the payment terms?
Simple halves: 50% at kickoff, 50% at acceptance — or milestone-based on larger programs. Set out in the proposal, never a surprise on an invoice.
Is there a guarantee?
A completion guarantee, in writing: if agreed deliverables aren't completed within the contracted scope, we keep working until they are, at no extra cost. What we won't promise is a specific revenue number before your baseline is measured — nobody honest can.
Is a retainer required?
No. Every engagement includes 30 days of post-launch support; after that a monthly retainer is optional — improvement, not dependency, is what it buys.
What if we want to stop or change scope mid-way?
Scope is fixed per engagement, so changes are handled as written amendments — agreed the same way the original scope was. You'll never discover a surprise on an invoice.
Do we need to replace our CRM or existing tools?
Usually not. We build on what you have wherever it's sound and only recommend replacement when a tool is genuinely the bottleneck. The architecture is what we're there to fix.
Which tools and platforms do you work with?
We're vendor-neutral: HubSpot, Pipedrive, and Salesforce on the CRM side; n8n, Make, and Zapier for automation; OpenAI and Anthropic models for AI; Slack, Microsoft 365, and Google Workspace around them — plus custom APIs where they earn their place.
Can you work with our IT team?
Yes, and we prefer it. Access is granted and scoped through them, everything we build is documented for them, and they can audit the whole system without us in the room.
Does this replace our sales team?
No — it removes the repetitive work around them. AI handles capture, qualification, data entry, and follow-up persistence; your people do the talking, judging, and closing.
We already have some automations. Do they survive?
The audit maps what exists, keeps what's sound, documents it, and replaces only what's broken or brittle. Working systems don't get rebuilt for the sake of it.
What does “Cirvix” mean?
Nothing, deliberately. Cirvix is a coined name — it carries no borrowed prestige and doesn't imply we're something we're not. We'd rather the work earned the reputation than the letterhead.
Where does our data live?
In your own accounts and your own tenant. We hold scoped, named access during the build and it's reviewed and revoked at handover.
Will you sign an NDA?
Yes — NDAs are standard before we see your pipeline, and a data processing agreement is available for EU data.
Is our data used to train AI models?
Never without your written consent. AI components are configured inside your accounts under the same rule.
Are you GDPR compliant?
We practice data minimization, honor access and erasure requests, and sign DPAs for EU data. Systems we build for you are architected the same way — your lawful basis, your data, your tenant.
Where can we see your security posture in detail?
The security page covers encryption, access control, our full vendor stack, retention, and what we deliberately don't claim — plainly, with nothing borrowed.
Which AI models do you use?
OpenAI and Anthropic models, chosen per task — qualification, drafting, and extraction have different sweet spots. Everything is built model-agnostic, so when better models ship, yours swap in without a rebuild.
What happens when the AI gets something wrong?
Every AI decision is logged with its reasoning, thresholds route uncertain cases to humans, and your team can override anything. We design for review, not blind trust — the system drafts and scores; people judge.
Where does the AI actually run?
Inside accounts you own — API keys, prompts, and workflows all live in your tenant. Nothing critical routes through infrastructure we control.
What does the 30-day support period cover?
Monitoring, fixes, tuning, and team training — we stay until the system is boring. It's included in every engagement.
Who maintains the system long-term?
Your team can — that's what the SOPs and documentation are for — or we do it under an optional retainer: monitoring, prompt updates as models evolve, new workflows, and a monthly review of the numbers.
How fast do you respond during support?
Within one business day, always; same-day for anything that stops leads from flowing. Broken revenue infrastructure is an emergency and gets treated like one.
What happens if something breaks after handover?
Every workflow ships with documentation and SOPs, so your team — or any competent operator — can diagnose and fix without us. If a retainer is active, it's our job and we're already watching.
How do we know it's actually working?
Week one measures your baseline — first-response time, manual hours, meetings booked, leakage. The system then reports its own delta on a live dashboard you keep. No vibes, just the numbers.
Can we extend the system later?
Yes — everything is built modular. New workflows land as retainer work or as a new fixed-scope engagement, on top of what already runs.
You're a small, founder-led firm — what if you're unavailable mid-engagement?
Two things protect you. Everything is built in your tenant and documented as we go — SOPs, runbooks, kill switches — so nothing we make is locked in our heads or our infrastructure; your team or any competent operator can pick it up. And payment is milestone-based: you never pre-pay for undelivered work, and everything delivered is already yours. Founder-led is a deliberate quality choice, engineered so you're never stranded.
What contracts do you sign — MSA, DPA, IP assignment?
A mutual NDA before we see your pipeline, a Master Services Agreement per engagement (fixed scope, acceptance criteria, agreed liability framework), and a Data Processing Agreement wherever EU data is involved. All IP created is assigned to you — accounts, code, prompts, and documentation in your name from day one. Your paper or ours.
Do you support SSO and our identity provider?
Yes. We build inside your identity and access model — named, least-privilege access provisioned through your IT (SSO / SAML, your identity provider, conditional access), used only for the build and revoked at handover. What we build authenticates through your existing controls, not a side door.
How do you handle liability, insurance, and our vendor risk review?
The MSA sets an agreed liability framework for the engagement. For formal vendor risk reviews — security questionnaires, insurance requirements, specific contractual terms — send them over and we answer line by line and meet what the engagement genuinely needs. We'd rather clear your procurement checklist up front than discover it at signature.
Can a founder-led firm deliver an enterprise engagement — and can we talk to a reference?
Scope is sized to what founder-led delivery ships well, in fixed phases with dates and acceptance criteria — we right-size rather than overpromise. We're taking a small number of founding engagements now: direct founder ownership, founding terms, and early clients become our first references. Ask on the call and we'll be straight about capacity and fit — and if we're not right for your size or timeline, we'll say so.
Still have a question?
Ask it live — thirty minutes, no pitch, straight answers.
Or write to umang@cirvix.com