Adding Chat, Video Calls and Scheduling to Your Product in 2026: Build, Use an API or Integrate

Communication features look small on a wireframe and turn into large builds. For most products the right mix is to integrate with the calendars and meeting tools your customers already use, buy video and chat infrastructure from a provider, and build only what makes your product different: who can talk to whom, what happens after a call, and how it’s paid for. Build calls from scratch on an open standard like WebRTC only when the call is the product. Below is a decision for each feature, what business buyers expect, the work nobody draws on the wireframe, and examples from our builds.

Why this replaced a 2022-2025 forecast

This post used to forecast the communication and collaboration market up to 2025. That window has closed, and a forecast never told a product team what to build. The questions below don’t expire. Should we build video calls or buy them? Do we need Outlook and Teams? What does chat cost us after launch?

Integrate, use an API or build: feature by feature

Feature	Integrate with existing tools	Use a provider’s API	Build it yourself
Scheduling	Microsoft 365 and Google calendars, so bookings land where people already look	Not needed for most products	Booking rules, reminders and who may book whom
One-to-one video calls	Meeting links from tools the customer uses, for business calls	A video API for calls inside your app	Calls directly on WebRTC, when calls are the core of the product
Group calls and live events	Rarely enough on its own	A streaming or events provider	Only at very large scale, with a team for it
Chat	Not usually	A chat API for delivery, history and push	Roles, moderation, translation and what chat connects to
Email and SMS notices	Not usually	An email or SMS provider	Which message goes to whom, and when

The “build it yourself” column is where your product lives. A tutoring app and a sales tool can use the same video provider and still be completely different products, because they differ in who meets whom, what gets recorded and what happens next.

Buying is cheap to start, and the bill grows with use. Twilio’s video pricing, current as of October 2026, is $0.004 per participant per minute, so a 30-minute call between two people costs 24 cents. Turning a recording into one video file adds $0.01 per composed minute. Chat providers usually price by monthly active users. Stream’s chat pricing is free up to 1,000 monthly active users, and its Start plan costs $399 a month billed annually, or $499 month to month, for up to 10,000. Put these numbers into your cost per customer before launch.

What business buyers expect: their own tools

If you sell to companies, your product has to work with the tools they already pay for. Zuzan, a scheduling tool for companies, started as an idea for a Calendly competitor and pivoted several times. Integrating Microsoft 365 was vital for selling to big businesses, so we built it in, along with the Microsoft Teams SDK and integrations for video calls and streaming. The case lists 60K subscriptions, 6K events a month, and up to 60 hours a month saved on scheduling meetings.

The platforms publish what you can do. Microsoft’s Outlook calendar API overview shows that an app can create and update events, look up free and busy times for people and meeting rooms, and suggest meeting times with findMeetingTimes, which weighs everyone’s free and busy status. Some of those features work only with work or school accounts, so check which accounts your buyers use. Events can also be set up as online meetings with providers such as Teams. The Microsoft Teams developer platform says Teams has over 320 million monthly active users and lets apps run across Microsoft 365. For Google users, the Google Calendar API exposes most of what the Google Calendar web interface can do.

WebRTC: what the standard covers

WebRTC is the open web standard for live audio and video between browsers. The W3C published it as a W3C Recommendation on 13 March 2025. It lets a browser send audio, video and other data to another browser or device.

It covers the media. Everything around the media stays your job: sign-in, who may call whom, waiting rooms, recording and who may watch the recording, what happens when a call drops, and how calls get paid for. Babystep, a platform that connects parents with learning experts for paid consults, used React and an RTC library for audio and video calls in its web app, next to schedules and payments. About six months in, it was clear the audience wanted a mobile app, and we added mobile developers to the team. Because the same team had built the web version, a lot of code carried over to the next stages.

At the far end of scale, Everytale, a platform for online events, uses WebRTC and WebSocket to handle 100,000+ users at the same time. An Amazon event on it reached over 500,000 viewers. Eleven of our specialists joined the client’s 25-person core team for that build. That’s a product where calls and streams are the core, and the team size reflects it.

The work nobody draws on the wireframe

• Time zones: Microsoft’s calendar API returns event times in UTC by default and keeps the original time zones in separate fields. Your booking screens, reminders and emails all have to agree.
• Permissions: who can start a call, who can join, and who can see a chat after someone leaves the group.
• Recordings and messages: where they’re stored, for how long, and who can delete them.
• Notifications: push, email and SMS, with limits so people don’t mute you.
• Moderation: report, mute and block, plus a person who acts on reports.
• Chat at scale: on Kosmo, a dating app with group and private chats and real-time chat translation, the chat infrastructure needed a new estimate after the discovery phase.

Paid calls and the App Store

If people pay for calls inside an iPhone app, Apple’s rules decide how you charge them. Guideline 3.1.3(d) of the App Store Review Guidelines allows payment methods other than in-app purchase for real-time services between two people, such as tutoring, medical consultations or fitness training. One-to-few and one-to-many real-time services must use in-app purchase. A one-to-one coaching app and a paid group class can sit in the same product and still need two different checkouts.

The US storefront has its own rules now. On 1 May 2025, Apple updated the guidelines after a US court decision, and apps on the US App Store may now include buttons, external links and other calls to action that point to other ways to pay. Elsewhere, guideline 3.1.1(a) allows them only in specific storefronts and with Apple’s entitlements. If you sell in several countries, plan the checkout per storefront.

How we would estimate your communication features

Once you know what to integrate, buy and build, you can see what your idea costs to build with our project estimate. It works in four steps:

1. Your brief becomes user stories, and each conversation type from your list can be one of them: booking rules, calls, chat, moderation, notifications and the checkout for each call type. You confirm what is in scope, so you see what each feature adds to the budget, and every hour traces back to a story you kept.
2. We check the hours the model suggests against what our team actually books on finished projects, then multiply by our published rate of $39-55 an hour. It’s a planning range, not a fixed quote.
3. For market size, the estimate suggests customer groups and gives each a TAM, SAM and SOM with a note on what the number covers. Treat them as hypotheses to test, not verified demand. Keep only the groups you would really sell to, and the market and unit economics are worked out only for those.
4. The unit economics show how many customers pay for the build and in which month it is paid back. You can change any starting number and the math updates.

What we would do

1. List every conversation your product needs: who talks to whom, one to one or in groups, live or not.
2. Ask your first customers which calendar and meeting tools they use, and integrate those first.
3. Buy video and chat infrastructure from a provider, unless calls are the core of your product.
4. Build the rules on top: who may book, call and message whom, what’s recorded and what happens after.
5. Settle payments per call type before design, using Apple’s person-to-person rule.
6. Test with real time zones, weak connections and a full group before launch.

Our web app development page covers browser video calls, live events and client portals. If the product is a subscription tool for companies, our SaaS development services page shows how we build one. The builds behind this guide are in the Zuzan case study and the Babystep case study.

FAQ

Should I build video calling from scratch?

Only if calls are the core of your product. Otherwise use a video provider’s API for calls inside your app, or meeting links from tools your customers already use, and spend your budget on the rules around the call.

What is WebRTC?

An open standard, published as a W3C Recommendation on 13 March 2025, that lets a browser send audio, video and other data to another browser or device. It covers the media, while sign-in, permissions, recording and payments stay with your product.

Can my app book meetings in Outlook and Teams?

Yes. Microsoft’s calendar API lets an app create and update events, look up free and busy times and suggest meeting times, and events can be set up as Teams meetings. Some of these features work only with work or school accounts.

Can an iPhone app take card payments for paid video calls?

For real-time services between two people, such as tutoring or medical consultations, Apple’s guideline 3.1.3(d) allows payment methods other than in-app purchase. One-to-few and one-to-many real-time services must use in-app purchase.

How much does it cost to add chat or video calls to an app?

It depends on how much you integrate or buy. With us, a first version of a web or mobile product typically costs $5,000-15,000 and takes 2-4 weeks, and larger builds are priced at $39-55 an hour after scoping. Usage comes on top: Twilio, for example, lists video at $0.004 per participant per minute as of October 2026.