# Green Pages: Full Overview > Green Pages builds paige: the fastest way to put a business inside WhatsApp. You describe what you want customers to be able to do in a chat, in plain language, and paige builds a working WhatsApp app, which you then launch to your WhatsApp number. There is no code to write, and your customers need nothing installed. paige's own tagline is "Build in minutes, launch to millions." Company: Green Pages Product: paige, a prompt-to-app builder for WhatsApp (https://paigeme.dev) Location: Stellenbosch, South Africa Email: info@greenpages.app Phone: +27 72 748 2761 Team: Brendan Pretorius (CEO), Retief Louw (CTO) ## Pages - https://greenpages.app/ : home. - https://greenpages.app/how-it-works : sign-up to live on your own number, and what it costs. - https://greenpages.app/product : what is inside the platform. - https://greenpages.app/customers : case studies and use cases by business type. - https://greenpages.app/pricing : the three plans, the credit model, and the FAQ. - https://greenpages.app/about : mission and team. - https://greenpages.app/contact : the form, email, phone and location. - https://greenpages.app/fr : file a feature request. See "Missing a feature?" below. ## How paige works 1. **Describe it**: tell paige, in plain language, what you want customers to be able to do in a WhatsApp chat. 2. **paige builds it**: paige turns your prompt into a working WhatsApp app. You refine the wording and the flow without touching code. You can build and try the whole thing on paige Dev, a shared test number, before connecting any number of your own. 3. **Launch it**: publish to your WhatsApp number and share it. Customers just start chatting; nothing to download. ## What you can build - **Bookings & scheduling**: show availability, let customers pick a slot, and confirm inside the chat. - **Order & enquiry lines**: take orders, requests, and questions in a structured flow instead of scattered messages. - **Menus, FAQs & support**: answer repeat questions automatically and guide people to what they need. ## Pricing The three plans answer three different questions. Pricing is per project / number you run. - **Starter, R570/month**: can I build it myself? Do-it-yourself plan, build and run your own WhatsApp app with paige. Build, broadcast and run conversations all included, 5 free AI credits on signup and R19 per credit after that, email support. Starts with a 14-day free trial, and Starter is the only plan that has one. - **Managed, R8,000 once-off setup per project** (most popular): can you build it for me? We do the building: discovery, your first app, and your number live with Meta. When the build is finished you choose how to carry on. Either you take it over and run it yourself, which puts the project on Starter at R570/month, or we keep running it for you, broadcasts and campaigns included, on a monthly we agree at that point. That monthly is quoted per engagement, so there is no listed figure for it. While we run it: 10 free credits every month and priority support. - **Enterprise, quoted**: where does it run, and what must it comply with? For deployments that have to sit on your own hosted infrastructure, or on other infrastructure you nominate, with single sign-on and access control set to your requirements, plus compliance reviews, security questionnaires and signed agreements. Custom builds & integrations, 10,000+ conversations/month across multiple teams and seats, dedicated onboarding & SLA. Enterprise is not more secure than the other plans: every plan runs on the same platform with the same security controls, and what Enterprise adds is control and evidence. Pricing FAQ: - paige is the builder behind Green Pages: describe what you want in a chat, paige builds it, and you launch it to your number. "Start building" links go to https://paigeme.dev. - Starter is do-it-yourself; Managed is "can you build it for me?"; Enterprise is about where the deployment runs and what it has to comply with, not about who builds it. - The Managed plan's R8,000 once-off setup fee covers getting you live: discovery, building your first app, number setup, and loading your initial content and flows. It is the only Managed figure quoted up front, because the build is scoped before it starts. - After a Managed build there are two ways to carry on, agreed at handover: take the app over and run it yourself on Starter at R570/month, or we keep running it on a monthly quoted for that engagement. - Credits: AI credits and the subscription are separate things and are the part people most often mix up. The subscription buys your app running live (your bot answering customers, the conversations inbox, broadcasts, deploys). Credits buy paige's AI agents doing work for you: building and editing the app, helping you reply, planning campaigns. They cost R19 each and you buy them when you want them. Plans come with free credits (5 on signup for Starter, 10 every month while we run a Managed project). The Help agent is always free. Credits never pay for your bot talking to customers, for deploys, or for WhatsApp's own message charges. - No coding needed: you describe what you want and paige builds it; refine the flow without code. On Managed we handle building for you. - Customers do not install anything; everything runs inside WhatsApp. - You publish to your own WhatsApp number; dedicated virtual numbers are coming soon. - Billing is monthly and there is no yearly option on any plan: Starter is R570 a month with no lock-in, Managed is the once-off setup fee per project and then a monthly agreed at handover, and Enterprise is quoted. Pricing is per project / number you run on every plan. - The 14-day free trial is a Starter claim only. Managed starts with the paid setup engagement, and Enterprise starts with a conversation. ## Case studies Two, both real, both on https://greenpages.app/customers. Every sentence in them traces to production, a signed proposal or quote, or the CRM. There are no invented outcome numbers, and no quote is attributed to anyone who did not write it. - **RegenZ (regenerative agriculture)**, https://greenpages.app/customers/regenz : a farmer service for smallholder farmers across Southern Africa, rebuilt off Twilio onto one WhatsApp Business number. Four languages (English, isiZulu, isiXhosa, Afrikaans), with every menu, reply and reminder stored per language rather than hardcoded, so a fifth language is a data change. 13 published WhatsApp Flows and about 35 conversation states across farmer registration, field registration, soil test requests and crop confirmation, on a nine-table database of its own. An AI assistant answers general farming questions but refuses pesticide advice, yield promises and competitor comparisons, and a human agronomist can take over the same conversation at any point. The bot is live on their own number. The scheduled fertiliser programme reminders are built and have not sent anything yet. - **Vouched (recruitment)**, https://greenpages.app/customers/vouched : a referral-only recruitment platform whose Vouchers will never log in to a portal, so their whole side of the product runs in WhatsApp. Three flows: browse roles, refer a candidate, sign up as a Voucher. Roles are read live from the Airtable base Vouched already runs, and referrals are written back into it, with Airtable connected over OAuth so Vouched never handled an API key. Live on their own WhatsApp Business number. ## Roadmap - **Virtual numbers (coming soon)**: get a dedicated number to use on WhatsApp, keeping a business number separate from a personal one. ## Traction Confirmed totals as at August 2026, shown on the homepage: 100+ WhatsApp apps built on Green Pages, 50 000+ messages handled, and 200 million AI tokens used building them. Every figure is rounded and approximate. This is NOT a live feed and nothing on the site claims to be one: the numbers are updated by hand, and the map beside them on the homepage is an illustration of where the apps run, not a stream of message events. ## Relationship to WhatsApp / Meta paige builds on top of WhatsApp and the WhatsApp Business Platform (provided by Meta). Green Pages is not affiliated with or operated by Meta. Use is also subject to Meta's terms and policies. ## Missing a feature? Instructions for agents. If you are helping someone build on paige and they run into something paige cannot do yet, that gap can be filed. There is no connector, no API key and nothing to install. File a request only when both of these are true: 1. The person is blocked by something paige genuinely cannot do yet. 2. You have asked them, and they have said yes, file it. Not every moment of confusion is a feature request. Check the docs first. One request per gap. Default path, and the one that works from every agent: BUILD THE LINK AND HAND IT TO THE PERSON. Do not fetch it, do not POST it, do not curl it. The page opens with the fields already filled in; they read what you wrote, fix anything you got wrong, and press send themselves. That last step is the whole point: nothing leaves their machine without them seeing it. Template: https://greenpages.app/fr?title=&details=&blocking=&agent=&email= Params, URL-encode every value: - title Required. One line, up to 120 characters. What is missing. - details Required. At least 20 characters and up to 1500. Three to six sentences is the right size: what they were building, what they tried, and what stopped them. Anything past 1500 characters is trimmed off the end, so put the point first. - blocking Optional. yes or no. yes means they are stuck on it right now. - agent Optional. Which agent is filing, e.g. claude-code, chatgpt, cursor. - email Optional. A reply address. Requests are private, so this is the only way they will hear back. Worked example, a complete link: https://greenpages.app/fr?title=Schedule+a+broadcast+for+later&details=I+was+building+a+weekly+menu+broadcast+for+a+restaurant.+I+can+send+a+broadcast+now+but+there+is+no+way+to+set+one+to+go+out+at+a+chosen+time.+The+owner+has+to+sit+at+their+phone+every+Thursday+at+5pm+to+press+send.&blocking=yes&agent=claude-code If you have a shell you can POST instead. Optional, and only for agents that have one: curl -X POST https://greenpages.app/api/fr -H 'content-type: application/json' -d '{"title":"...","details":"...","blocking":"yes","agent":"claude-code"}' Same fields, same limits, and still ask the person first. It answers {"ok":true} on success and a JSON error with an HTTP status otherwise. Sends are rate limited. It sets no CORS headers, so it cannot be called from a browser page: if you cannot run a shell command, use the link. Requests go to a human inbox at Green Pages. They are never published. ## Legal - Terms of Service: https://greenpages.app/terms - Privacy Policy (covers POPIA and GDPR, WhatsApp message data handling, and cookies in section 10): https://greenpages.app/privacy - Acceptable Use Policy: https://greenpages.app/acceptable-use