Yielde
Frequently asked
The questions buyers actually ask before signing up. Answered straight, with the trade-offs visible.
Do my prompts and customer data train an AI model?
No. Every model call routes through our LiteLLM gateway to the chosen provider (OpenAI gpt-5, Anthropic Claude). Provider terms forbid training on API traffic, and we do not store prompts or completions beyond the request lifecycle of the workflow that fired them. The gateway exists so we can rotate keys, attribute cost per workflow, and redact upstream at one place — not so we can hold your data.
Are you POPIA compliant?
Yielde is the operator (processor); you remain the responsible party for your customer data. Before your workspace is provisioned, we sign a Data Processing Agreement with you through Documenso. POPIA Section 19 obligations (integrity and confidentiality) inform our auth, encryption, webhook signing, and per-tenant isolation choices — see /security for the full picture.
If a formal third-party audit (SOC 2, ISO 27001) is a hard requirement for your business, tell us before signing up. We do not hold those certifications yet and will be straight about timelines.
What does "setup" actually involve?
Five concrete steps. (1) Sign up with your email — magic link, no password. (2) Sign the DPA in your dashboard via Documenso. (3) Add a card; the first invoice clears (the activation gate). (4) We provision your workspace on AWS in Cape Town — your subdomain, n8n container, LiteLLM virtual key. (5) We sit with you for an hour to wire up the sources you want (Gmail / WhatsApp / web form / voice number).
Steps 1–4 are self-serve and usually take an evening. Step 5 is human-in-the-loop and gets scheduled inside the first week.
Why is pricing in ZAR? I am not in South Africa.
Paystack is our primary billing rail and it is ZAR-native. If you are outside South Africa, ask us about Stripe — we run it on request for non-ZAR tenants and the integration is an evening of setup. Pricing for non-ZAR is at the same exchange rate, no margin tacked on.
What are "credits", and what happens if I go over?
Every plan includes a monthly pool of credits that runs your automations. A credit is a unit of AI usage — every model call your workflows make draws from that pool. Most operators stay well inside their plan.
If you use more than your monthly pool, you are not cut off and there is no surprise tier upgrade. The extra usage is billed at a simple metered rate, and your month-to-date usage is always visible in your dashboard so there are no surprises at invoice time.
Can I cancel any time?
Yes. On monthly billing there is no lock-in — cancel any time. If you choose annual billing for the ~17% discount, it is prepaid for the year. You can cancel from the Billing tab in your dashboard or by emailing support@yielde.dev. The cancellation policy is on /cancellation-policy.
When you cancel, your workspace stops on the next billing date. Your dashboard and data stay readable for a 30-day grace period in case you change your mind, and you can request a copy of your data before it ends.
What happens if OpenAI or Anthropic goes down?
The LiteLLM gateway lets us swap models without your workflows changing. For customer-facing surfaces (voice receptionist, chatbot), failover is wired so the conversation continues on a backup model rather than dying. For batch workflows, the workflow retries on the next provider in the chain and Sentry alerts us if the chain is exhausted.
We will not pretend an upstream outage is zero-impact — a 90-second backup-model fallback feels different from the primary. But your tenant does not go dark.
Do you work with my existing CRM?
Almost certainly. HubSpot and Pipedrive are an evening of n8n wire-up. Salesforce, Zoho, and Microsoft Dynamics are on the roadmap and a paying tenant with a hard requirement pulls them forward. Google Sheets and Airtable work today if you have not picked a CRM yet. See /integrations for the full list.
Why not just build this on n8n / Zapier / Make myself?
You can. If you have an in-house operator who likes plumbing, that is a real option. What you do not get with a DIY build: the LiteLLM gateway (model rotation, cost attribution, redaction), the voice receptionist on Retell (~700 ms latency), the per-tenant isolation, the POPIA DPA, the 24/7 monitoring, or the lifecycle gating that means a missed payment pauses a workspace cleanly instead of leaking a service to someone who has not paid.
If you are paying a developer R30k/month to maintain a DIY stack, Yielde is cheaper. If you are paying R0/month because the founder built it on a weekend, Yielde is more expensive and may not be worth it yet. That is a real trade-off — we are not the right tool for every business at every stage.
What happens if I miss a payment?
Your workspace transitions from `active` back to a paused state — workflows stop firing, voice calls roll to voicemail, the dashboard tells you exactly what happened with a 'recover' button to retry the payment. We do not delete anything. Customer data stays put until cancellation grace ends.
You will hear from us before that point — we email after the first failed retry and again 48 hours before the workspace pauses.
Who owns the workflows you build for me?
We do. The workflows, prompts, and configurations are Yielde intellectual property — they are how we deliver the service, and they are not exported or transferred when you cancel.
What is always yours is your data — customer records, transcripts, and CRM entries, which you can request a copy of before your grace period ends — plus the third-party accounts the automations operate in, which you can revoke at any time.
Still unsure?
Email support@yielde.dev with the specifics of your operation — number of inbound contacts, current stack, what breaks. We will tell you whether Yielde is a fit, what it would take to onboard, and where it is honestly the wrong tool.