Mike is an experienced Product Manager who focuses on all the “non-development” areas of My AskAI, from finance and customer success to product design, copywriting, testing and more.
Kommunicate starts at $40/mo and launches a bot in about ten minutes. But it trains on your docs rather than your tickets, and its "predictable" pricing hides per-conversation overages. Here's the reality.
Someone has forwarded you Kommunicate as the cheap way to put AI on your support, and now you are the one who has to work out whether it actually holds up. I've had that conversation more than once.
It starts at $40 a month, gets a chatbot live in about ten minutes, and lists every messaging channel you could want. The reality underneath is more mixed: it trains on your documents rather than your past tickets, the "predictable" pricing has overage charges, and the company behind it is small. None of that makes it a bad choice; it just makes it one I'd want you to understand before you commit.
I'd bet you are in one of three situations:
You already run live chat and want to bolt on an AI chatbot without ripping anything out.
You tried one of the free chatbot generators and you are wondering whether the paid tiers are worth it.
You are trying to model the conversation-based pricing and the overage maths keeps not adding up.
Either way, I'll break down what Kommunicate is, how it works, what channels and knowledge it supports, where the limitations bite, what resolution rate to actually expect, what it costs, and who it suits, so you can decide without regrets.
What is Kommunicate?
⚡
TL;DR: Kommunicate is an SMB-focused AI chatbot platform: a no-code Kompose bot builder, model-agnostic generative AI and built-in human handoff, built by the ex-Applozic team.
Kommunicate is an AI-first customer-service automation platform aimed at small and medium businesses. Its own WordPress plugin listing describes it word for word as "an AI-first customer service automation platform for small and medium-sized businesses," and the homepage pitches controllable, gradual AI adoption: "AI that knows when to answer, when to escalate, and when to step aside."
In support-team terms, it is three things stacked together: a chat widget and omnichannel front end, a no-code bot builder called Kompose, and generative AI answers with built-in human handoff.
Kommunicate homepage
A bit of history explains a lot about the product. Kommunicate launched in 2018 as a second product inside Applozic, the in-app chat-SDK company its founders ran first. Applozic's chat-SDK business was wound down in April 2022 and the team moved fully onto Kommunicate; the legal entity today is Intentive Technologies (a name you only see in the small print).
That lineage is why the GitHub org carries unusually deep mobile SDKs: the iOS SDK is explicitly forked from Applozic's old one.
The product spans six pieces: a Generative AI Chatbot, the Kompose no-code agent builder, a Voice AI Agent, AI Email Ticketing, Live Chat, and an FAQ Chatbot. Roughly 72% of its customers sit in the 0-100 employee band, which tells you who it is really built for.
On G2 the picture is positive but thin, so I'd read the texture of the reviews over the score itself. The line that recurs is speed:
G2: Kommunicate scores 4.8/5 from 24 reviews on G2. "Very easy to integrate and deploy in website. We could deploy the chatbot within 10 mins." via a G2 reviewer (Founder, Small-Business).
The counterweight sits in the same place: another reviewer notes that "sometimes the bot feels a bit buggy and the mobile app is not the most responsive."
💬
My AskAI sits next to this rather than on top of it. Kommunicate is a separate chat platform that connects to your helpdesk; My AskAI is the AI agent that lives inside the helpdesk you already run (Zendesk, Intercom, HubSpot, Freshdesk or Gorgias).
How easy is it to set up Kommunicate?
⚡
TL;DR: Setup is fast, a working bot in about ten minutes via Kompose, but signup needs a business email and the best helpdesk integrations are gated to higher tiers.
Setup is genuinely the strongest thing reviewers say about Kommunicate. Word-on-the-street, and the most-cited praise across G2 and Capterra, is getting a working bot live in about ten minutes through the Kompose drag-and-drop builder. "As a coding newbie, I was thrilled with how easy Kommunicate's AI chatbot was to set up," is a representative review.
Setting up a Kommunicate AI agent, from the docs
Two things slow that down in practice. First, signing up requires a business email (Gmail and personal addresses are blocked), which shuts out hobbyists and anyone trialling it on the side. Second, the integrations you probably care about are gated to higher tiers: Zendesk and Freshdesk need the $200-a-month Professional plan, and Salesforce, HubSpot and Zapier need Enterprise.
💬
My AskAI also sets up in around ten minutes, and its helpdesk integrations are not held back behind a higher tier: the same agent works across every supported helpdesk on any plan.
What channels does Kommunicate work in?
⚡
TL;DR: Web, WhatsApp, Messenger, Instagram, Telegram, Line, email and voice, plus best-in-class mobile SDKs. There is no SMS and no Intercom integration.
Kommunicate is genuinely broad on channels. Natively it covers the web widget, WhatsApp, Facebook Messenger, Instagram DMs, Telegram and Line, plus email through AI Email Ticketing and voice through its Twilio-backed Voice AI product. Slack is supported for team notifications.
Kommunicate's social and messaging channels
Two gaps matter to me as a buyer. There is no SMS, which one third-party reviewer flags bluntly: "want Telegram, Instagram DM, Viber, Signal, or SMS? You are out of luck."
And there is no Intercom integration at all; Kommunicate positions itself as an Intercom competitor rather than a companion.
Where Kommunicate genuinely leads is mobile. Its open-source SDKs cover iOS, Android, Flutter, React Native, Ionic and Cordova/Capacitor, all on GitHub, and that depth is hard for web-first competitors to match. If your product is a mobile app that needs in-app AI chat, this is a real advantage I wouldn't talk you out of.
💬
My AskAI takes the opposite approach: rather than being a separate widget with its own SDKs, it runs natively inside Zendesk, Intercom, HubSpot, Freshdesk and Gorgias, so the AI answers in whatever channels your helpdesk already routes to it.
What are the limitations of Kommunicate?
⚡
TL;DR: The big ones: it learns from docs rather than your past tickets, reporting is shallow, the "predictable" pricing carries per-conversation overages, and the vendor is small (about 16 staff).
If you are evaluating seriously, these are the constraints I'd want on the table rather than the marketing ones.
It learns from documents rather than your past tickets. Kommunicate's generative AI product is grounded on website URLs, PDFs, spreadsheets, help center articles and FAQs. Historical support tickets are not on that list, which assumes your documentation is already complete and current, and leaves out the practical knowledge that only lives in how your agents have actually answered customers.
Reporting is shallow. A Capterra reviewer put it bluntly: "Reporting is very poor, advanced analytics cannot be done." You can see what happened, but getting to why a bot is escalating a fifth of its chats is harder than the dashboards suggest.
Pre-built flows can dead-end. Kompose is built around intent and flow design, which is fine for predictable conversations but can feel rigid when a customer goes off-script, and the same reviews that praise the setup also concede the bot "feels a bit buggy" at times.
Legacy bugs and mobile instability surface. The longest detailed Capterra review, from a two-year customer, describes the web dashboard not showing the same conversations as the mobile app, chat histories not displaying, and out-of-date integration documentation. App Store reviews echo it: "Sometimes I go to respond to a chat and the app closes or crashes."
The "predictable" pricing has overages. Kommunicate's pitch is conversation-based pricing as a calmer alternative to per-resolution billing, but it charges $15 per 1,000 conversations over your limit on Starter and $10 per 1,000 on Professional. Kommunicate's own Chargebee case study credits the hybrid usage-and-seat model with lifting its revenue per customer by about 40%, which is another way of saying customers pay more.
It is a small vendor.Tracxn lists around 16 employees as of mid-2025, down roughly 46% year on year, against about $437K total raised across three small rounds. There is also almost no organic community discussion, and for a tool you are wiring into your support stack, vendor longevity is a fair thing to weigh.
💬
My AskAI is built around the opposite of the first two points: it trains on your past resolved tickets, it lives inside your helpdesk so there are no separate silos to reconcile, and your team can ask Echo why the agent gave any answer and which source it used, so the reasoning is auditable rather than opaque.
What knowledge sources can I train Kommunicate on?
⚡
TL;DR: Website URLs, PDFs and documents, help center articles and FAQs are all supported. Your historical support tickets are not an ingestion source.
Kommunicate trains its AI on website URLs, uploaded PDFs, documents and spreadsheets, help center articles (it can pull from Zendesk Guide, Salesforce Knowledge and Help Scout), and FAQs. It describes this as RAG-grounded ("controlled responses … using RAG"), so answers are drawn from the material you give it.
Training-source comparison: Kommunicate trains on URLs, docs, help-center articles and FAQs but not past tickets; My AskAI adds past tickets.
The catch is the one from the limitations section: your historical support tickets are not an ingestion source. If your written documentation is thin, the bot starts thin.
💬
That last point is worth dwelling on, because it is a trap for any team without a tidy help center. My AskAI trains on past tickets as well as documents, and it connects to a wider set of sources: Google Drive, Notion, Confluence, SharePoint, OneDrive, Dropbox, Salesforce and Shopify. If you do not have polished docs yet, we can train on your historic resolved tickets to generate starter knowledge from scratch, so you are not blocked on writing a knowledge base first.
What features does Kommunicate have?
⚡
TL;DR: Three layers: a generative-AI chatbot, the Kompose no-code builder, and agent-assist (suggestions, summaries, translation, insights), plus standalone Voice AI and AI Email Ticketing.
I'd group Kommunicate's feature set into three layers, the way the product itself does.
Kommunicate's three layers: a generative AI chatbot, the Kompose no-code builder, and agent-assist tools.
The autonomous layer is the Generative AI Chatbot: RAG over your knowledge, model-agnostic, with configurable escalation. The builder layer is Kompose, a no-code drag-and-drop Flow Designer with intents, entities, webhooks, fallback intents, inline JavaScript for dynamic responses, and handoff nodes. The agent-assist layer adds AI Suggestions for real-time reply recommendations, AI Summary for long threads, real-time AI Translation, and AI Insights for natural-language questions over conversation data.
On top of those, Kommunicate also sells a standalone Voice AI Agent and AI Email Ticketing as separate products (handy if voice or email-only is your main channel), and a 2025 release added token-by-token streaming responses to cut latency.
Kommunicate's Kompose bot builder, from the docs
💬
My AskAI replaces flow-builders with Tasks and Tools: natural-language, multi-step actions (refunds, order updates, account changes) that run right inside your helpdesk, no decision trees to maintain.
How do I improve Kommunicate's responses?
⚡
TL;DR: There is a feedback loop and a bot-accuracy review, but shallow analytics mean improvement is more manual than the dashboards suggest.
Kommunicate gives you a feedback loop: bot-accuracy review, auto-resolve for dormant chats, and configurable escalation rules you can tune over time. The mechanics are there.
Kommunicate's AI agent feature set
What is harder is knowing what to fix. Because the analytics are shallow, improvement leans on you watching conversations and inferring the pattern rather than the tool surfacing it. I wouldn't treat this one as set-and-forget; that is how answer quality drifts.
💬
My AskAI approaches improvement the other way round: we draft new knowledge articles every week by comparing the AI's replies against your human agents' replies, and your team can ask Echo to investigate a specific conversation and explain where the answer came from. The improvement loop does more of the work for you.
What resolution rate can I expect from Kommunicate?
⚡
TL;DR: Kommunicate markets 85% automated resolution, but real case studies land nearer 40-60% deflection, and deflection is not a confirmed resolution.
Kommunicate's homepage headlines an 85% automated resolution rate, a 40% CSAT lift and a 60% reduction in human handoffs, and elsewhere claims "up to 95% query resolution." I'd treat those as aspirational ceilings; no single published case study validates the aggregate.
The real customer numbers land lower and, importantly, mostly measure deflection rather than confirmed resolution. Crunch reports its chatbot handling about 60% of customer-service requests; BTVI cites 40% conversation deflection; a generic case study cites 43% deflection and a 50% overall reduction. The gap between "automated resolution" and "deflection" is a real one: a deflected chat is not a solved problem.
Kommunicate markets 85% automated resolution; real case studies report around 50% deflection; the field median is 70%.
For context, our own field benchmark across roughly 55 vendors and 195 deployments puts the median AI-handling rate at about 70%, per our field benchmark of AI resolution rates. The single biggest caveat: the label moves the number more than the capability does. "Resolution" reads about 12 points higher than "automation" because every vendor counts a different event.
So an 85% automated-resolution headline is not really comparable to a 70% resolution median. I'd treat any vendor's published rate as directional rather than a guarantee; across our own customer base, My AskAI averages 72%.
💬
My AskAI averages a 72% resolution rate on a rolling 30-day basis across its whole customer base, and every reply is auditable: ask Echo why any answer was given and which source it used.
What AI model does Kommunicate use?
⚡
TL;DR: Model-agnostic: it routes answers through OpenAI, Anthropic, Gemini, Dialogflow, Lex or Watson, with no proprietary model of its own.
Kommunicate is model-agnostic. It routes generative answers through whichever provider you choose: OpenAI, Anthropic, Google Gemini, Dialogflow, Amazon Lex or IBM Watson, with a dedicated integration page for each. It has no proprietary model of its own, and the exact model versions surfaced in the dashboard are not publicly documented.
Kommunicate sells that model choice as a feature, and it is worth a contrarian note, because we get the "what model do you use?" question a lot. It is a reasonable question if you do not work in this every day, but I think it is the wrong one on two levels.
First, picking the model is the vendor's job rather than the customer's. Only the vendor can see across every customer's data how each model moves resolution, accuracy and escalation, and models shift week to week.
Second, the premise that an agent is one model is itself the tell. A real agent fires upwards of ten orchestrated LLM calls between question and answer (one rewrites the conversation, one detects the language, one applies guidance and tone, one decides whether a task should run), each tuned for a different job. If a vendor can answer the model question in one word, that usually means the setup is question-in, one prompt, answer-out, which is not where good answers come from.
That is why we run a multi-model architecture across OpenAI, Google and Anthropic and A/B test each step continuously, rather than reducing it to a single model name.
💬
My AskAI runs a multi-model architecture (OpenAI, Google and Anthropic) and A/B tests each step continuously, so picking and managing the model stays our job rather than yours.
What languages does Kommunicate work in?
⚡
TL;DR: 120+ languages, with dedicated landing pages for several and real-time AI translation for agents. This is one of Kommunicate's genuine strengths.
Kommunicate supports 120+ languages, with dedicated landing pages for Arabic, Spanish, French, German, Portuguese, Italian, Swedish, Russian and Hindi, plus real-time AI translation so agents can handle conversations in languages they do not read.
💬
My AskAI auto-detects 95 languages per message and offers Live Translation for agents, so the multilingual story is comparable. Kommunicate's headline count is genuinely high, though (fun fact: 120+ is more languages than most of its rivals even advertise), so if raw language breadth is your priority it has the edge.
How secure is Kommunicate?
⚡
TL;DR: Kommunicate lists SOC 2, ISO 27001, GDPR and HIPAA via a Sprinto trust portal, though it does not surface a downloadable third-party audit report.
Kommunicate's trust portal lists SOC 2, ISO 27001, GDPR and HIPAA as compliant, managed through Sprinto. One caveat for security reviewers: the public portal asserts compliance but does not surface a downloadable SOC 2 Type II report or a third-party-audited ISO certificate, and it does not distinguish SOC 2 Type I from Type II. The data processing agreement is also still published under the original Applozic legal entity.
💬
My AskAI is SOC 2 Type II certified and GDPR compliant, with AES-256 encryption at rest and TLS in transit, and customer data is never used to train models or shared outside that customer's own ticket handling. The cleaner differentiator on security is verifiability: your team can ask Echo exactly why any answer was given and which knowledge source it used, so the audit trail is something you can actually inspect rather than take on trust.
Who is using Kommunicate?
⚡
TL;DR: Mostly SMBs (about 72% have 0-100 staff). Named case studies include Crunch, TelOne, Brash Solutions and Oklahoma City Community College.
Kommunicate's customer base skews small: about 72% have 0-100 employees and only 1.7% are global enterprises, so the enterprise logos it shows (Rakuten, Bridgestone, KPMG, Amgen, HDFC Life) are most likely small contracts within those companies rather than wall-to-wall deployments.
Its named case studies are more representative of who actually buys it. Crunch reports its chatbot handling about 60% of customer-service requests after replacing Salesforce Live Chat; TelOne handled more than 20,000 unique conversations a month; Brash Solutions automated 500+ daily chats; and Oklahoma City Community College reported a CSAT of 8.33 after a Moodle integration.
TL;DR: Conversation-based pricing: Starter $40/mo, Professional $200/mo, Enterprise custom, with $10-$15 per 1,000-conversation overages and no free plan.
Kommunicate uses conversation-based pricing (a mix of conversation volume, seats and AI-agent quota), billed on conversations rather than resolutions. Its pricing page lists three tiers.
Plan
Monthly (annual)
AI agents / seats
Conversations
Overage
Starter
$40 ($34)
1 / 1
250 / mo
$15 per 1,000
Professional
$200 ($167)
2 / 3
2,000 / mo
$10 per 1,000
Enterprise
Custom
Custom
Custom
Negotiated
Kommunicate Starter and Professional
Starter is $40 a month ($34 on annual): one AI agent, one seat, 250 conversations a month, the web, mobile, WhatsApp, Telegram and Instagram channels, AI email automation, and three months of history. Professional is $200 a month ($167 on annual): two AI agents, three seats, 2,000 conversations a month, the Zendesk, Freshdesk, Google Analytics and phone-call integrations, plus AI Summary, auto-resolve, agent assist, campaign messaging, API and webhook access, and a year of history. Enterprise is custom and adds Salesforce, HubSpot and Zapier, SSO, white-label and a dedicated account manager.
Kommunicate's pricing tiers
A "conversation" is all the messages in a single session (worth pinning down, since it is the thing you are billed on), roughly 40 messages by Kommunicate's own ratio of 250 conversations to about 10,000 messages.
Overages and the "predictable" pricing caveat
The predictable-pricing story has a real asterisk: go over your conversation limit and you pay $15 per 1,000 conversations on Starter or $10 per 1,000 on Professional. That is the same kind of variable cost Kommunicate criticizes in per-resolution pricing (a little ironic, I think), and a no-op chat still counts as a conversation. There is no permanent free plan, though there is a 30-day free trial with no credit card on every tier.
Kommunicate's advertised price is $40 Starter or $200 Professional; the real bill adds overages, seat fees and counts no-op chats.
Pricing history
This model is fairly new. Through 2022-2024 the tiers were "Lite" at $100 and "Advanced" at $200 with a free plan; earlier still, pricing was based on monthly active users. The move to conversation-based pricing (and removing the free plan) is recent, and the Chargebee case study credits it with a 40% jump in revenue per customer.
💬
My AskAI prices differently again. It charges per ticket rather than per resolution or per conversation, at roughly $0.10 a ticket, on plans of $199 a month (Pro, 1,000 credits) and $499 a month (Scale, 2,000 credits). The point of per-ticket billing is that your bill stays flat as the AI gets better, where per-resolution models charge you more precisely as resolution improves.
On a worked example of 10,000 tickets a month at a 75% resolution rate, My AskAI on Scale comes to about $1,299 a month, against roughly $7,425 for Intercom Fin and $11,250 for Zendesk AI. And before you pay anything there is a 30-day free trial with every feature unlocked, unlimited tickets and no card required, so I'd prove it on your own volume first.
I Let AI Agents Resolve 10,000 Support Tickets, Here's How Much It Cost
Does Kommunicate have a free trial?
⚡
TL;DR: Yes, 30 days with no credit card on every plan. There is no permanent free plan any more, and signup needs a business email.
Yes: 30 days, no credit card, on every plan. What there is not, any more, is a permanent free plan; the old free tier was removed when Kommunicate moved to conversation-based pricing. Signing up does require a business email.
💬
We run a 30-day free trial too, with all features unlocked and no card.
Is Kommunicate worth it?
⚡
TL;DR: Worth it for mobile-app or omnichannel SMBs that want a cheap, model-agnostic no-code chatbot. A weaker fit on Intercom, for past-ticket training, or for deep analytics.
Kommunicate is worth it if you are a mobile-app or omnichannel-messaging SMB that wants a cheap, fast, no-code chatbot and values model choice. The mobile SDK depth, the WhatsApp and Telegram reach, and the low-code Kompose builder are genuine strengths at this price.
✅
Choose Kommunicate if…
Your product is a mobile app that needs in-app AI chat through a native SDK.
You want to pick your own LLM (OpenAI, Anthropic, Gemini and more) rather than being locked to one.
WhatsApp, Telegram and Instagram are core channels for your support.
You are an SMB on a tight budget that wants a low-code flow builder live in minutes.
❌
Don't choose Kommunicate if…
You run support inside Intercom, where there is no integration.
You want the AI trained on your real past tickets rather than just polished documents.
You need deep deflection and knowledge-gap analytics to improve over time.
You want a helpdesk-native agent with SMS support and a larger vendor behind it.
What are the Pros and Cons of Kommunicate?
Pros
Fast to launch. A working bot in about ten minutes via the Kompose drag-and-drop builder is the most consistent praise in its reviews.
Model choice and best-in-class mobile SDKs. LLM-agnostic across OpenAI, Anthropic, Gemini and more, plus open-source SDKs for iOS, Android, Flutter, React Native, Ionic and Capacitor.
Built-in human handoff at an SMB price. Rule-based escalation and a shared inbox that competitors a tier up charge much more for.
Cons
Learns from documents rather than your past tickets. The knowledge model assumes your docs are complete and current (see Knowledge sources and Limitations).
Shallow reporting. "Reporting is very poor, advanced analytics cannot be done," per its own reviews (see Limitations).
"Predictable" pricing carries overages. $15 per 1,000 conversations on Starter reintroduces the variable cost it criticizes elsewhere (see Pricing).
Small vendor. Around 16 employees and roughly $437K raised is a fair longevity concern for a stack tool (see Limitations).
⭐
Kommunicate
Brand: Intentive Technologies
Rating: 6.5/10
In a sentence: a capable, fast-to-launch SMB chatbot builder with genuinely strong mobile DNA, held back by docs-only training, shallow analytics, conversation-pricing overages and vendor-scale question marks.
💬
Want an AI agent that lives inside Zendesk, Intercom, HubSpot, Freshdesk or Gorgias and trains on your past tickets? Try My AskAI free for 30 days, all features unlocked, no card.
FAQs
What is Kommunicate used for?
In practice, teams use Kommunicate to automate customer support with an AI chatbot, live chat and agent-assist tools, mostly at small and medium businesses. It combines a no-code bot builder with generative AI answers and human handoff across web, mobile and messaging channels.
Is Kommunicate free?
No. There is no permanent free plan any more (it was removed when Kommunicate moved to conversation-based pricing). There is a 30-day free trial with no credit card on every tier.
How much does Kommunicate cost?
Starter is $40 a month, Professional is $200 a month, and Enterprise is custom-priced. All tiers bill on conversation volume plus seats, with overage charges of $10-$15 per 1,000 conversations once you pass your limit.
What's the difference between Kommunicate and Intercom?
Kommunicate is a cheaper, SMB-focused chatbot builder that competes with Intercom rather than integrating with it (there is no Intercom integration). It uses conversation-based pricing, where Intercom's Fin uses per-resolution pricing.
Does Kommunicate integrate with Zendesk?
Yes, but the Zendesk integration requires the Professional plan at $200 a month, which is worth knowing if Zendesk is your reason for buying. Freshdesk is on the same tier; Salesforce and HubSpot need Enterprise.
Does Kommunicate work with Intercom?
No. Kommunicate has no Intercom integration and positions itself as an Intercom alternative. If you run support inside Intercom, you would need an AI agent that works natively there instead (which is exactly the gap we fill).
What AI models does Kommunicate use?
Kommunicate is model-agnostic and routes answers through OpenAI, Anthropic, Google Gemini, Dialogflow, Amazon Lex or IBM Watson. It has no proprietary model, and the specific model versions are not publicly documented.
Can Kommunicate train on past support tickets?
No, and this is the gap I'd flag hardest. Kommunicate trains on website URLs, PDFs and documents, help center articles and FAQs, but not on your historical support tickets. Teams that want the AI to learn from past resolved tickets (like ours does) need a tool that ingests them directly.
Does Kommunicate support WhatsApp?
Yes. WhatsApp is a native channel, alongside Facebook Messenger, Instagram, Telegram and Line. It is one of Kommunicate's stronger areas (and I rate it here).
Does Kommunicate support SMS?
No. SMS is not a supported channel, which third-party reviewers flag explicitly. If SMS is part of your support mix, you will need another tool for it.
How many languages does Kommunicate support?
Kommunicate supports 120+ languages, with dedicated landing pages for several and real-time AI translation for agents. Raw language breadth is genuinely one of its strengths, and I wouldn't argue otherwise.
What is Kompose?
Kompose is Kommunicate's no-code bot builder: a drag-and-drop Flow Designer with intents, entities, webhooks and inline JavaScript. It is what most reviewers mean when they say the platform is fast to set up.
Mike is an experienced Product Manager who focuses on all the “non-development” areas of My AskAI, from finance and customer success to product design, copywriting, testing and more.