ChatFrom
AI chatbot provider to small teams, built from your docs
AI & Machine Learning·Productivity·HR & Recruiting·Operations & Logistics
What is ChatFrom?
ChatFrom builds an AI chatbot from your own documents and website, and puts it to work wherever you need it. Add your help pages, policies, price lists, manuals and PDFs, or point it at your site, and it answers from that content, day and night.
It is not only for customer support. Businesses use it to answer customers, look up orders and handle returns, manage subscriptions, book meetings, collect leads and quotes, guide signed-in users inside their own product, and give their own team an internal assistant for HR questions and company knowledge.
It runs wherever people write: a chat widget added to your site with one script tag, a share link, inside your own app, and in WhatsApp, Telegram, Slack, Discord, the Crisp chatbox and email. The same knowledge and tools work in every channel, in the language each person writes in.
Built-in tools look up Shopify orders and request returns, show or cancel a Stripe subscription once the customer proves their email, add rows to Google Sheets, book meetings in Cal.com or Calendly, and take call-back requests. Anything else connects through your own API or an MCP server, and a visual workflow canvas handles tasks with several steps. When a person is needed, it hands the conversation to your team by email, Slack or Crisp.
You stay in control: choose from eight AI models by OpenAI, Anthropic, Google and Mistral, correct a weak answer from the conversation log with one click, and test changes with evaluations on your own questions.
Pricing is flat: Free to start, Pro at $29 a month for about 5,200 answers, and Business at $49 for about 14,800. There are no fees per seat or per conversation, and nothing is charged past your plan. ChatFrom is hosted in Frankfurt, Germany, with a DPA available, and its chatbot engine is open source.
Ready to launch?
Submit your product and get discovered by builders and creators worldwide.
Launch Now
FounderPlaybooks.
What other founders did to grow.
2722 dispatches from hundreds of founders, pulled from the week's best podcasts.
you really want to be smart about what each individual user is seeing and making sure that it's not too much... if you're running like you know four or five different like packages in terms of like weekly monthly quarterly annual um and then you're also doing like three different monetization methods it can become a lot
Serve one monetization model per user segment, not all at once
As hybrid monetization grows, the risk is overwhelming each user by showing every model simultaneously — weekly, monthly, quarterly, annual plans plus ads plus usage credits. The fix is to run many variants but ensure each user sees only one clear, well-matched offer at a time. One well-chosen offer for the right segment converts better than three mediocre options fighting for attention.
The color of the button, the language — a lot of that really translates across the portfolio. But the offering — whether we offer annual or monthly, free trial or not — that's more nuanced and we tailor it to the product.
Paywall design insights port across apps; pricing and offer structure must be tailored per product
Running 37 apps gives Maple Media a natural A/B testing laboratory. UI and copy learnings (button colour, CTA language) generalise well and get applied portfolio-wide. But offer mechanics — trial length, annual vs monthly default, premium model vs ads — must be matched to how and why users pay in each specific category. Separating the transferable from the bespoke saves time without sacrificing conversion.
There's a play for whatever you're stuck on.
Read all 2722 playbooks