PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Engagement scope - proposed scope

Choosing a White Label Messaging App Provider: Four Routes, Compared

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Scope areas for this kind of build

Typical scoping questions

Who holds the source code?

  • Ask for the repository by name and ask whether any tier withholds it. A license to use an app is not ownership, and the gap shows the first time you need a screen changed.

Where do members and messages sit?

  • On your database or on the seller's. Confirm which, and confirm how you would export everything if you left. That data is the asset you are building.

What happens when you stop paying?

  • With a rental the service can go dark with the invoice. With a platform you own you carry on with a hosting bill and your third-party services. Insist on the answer in writing.

What does a report do?

  • Have them file one and show you where it lands. A queue with reasons you write and a way to block a whole group is moderation. An email to an inbox is only a notification.

Can a colleague rebrand it?

  • Ask someone in operations to change the app name and a color while you watch. If that needs an engineer, the product is reusable but you cannot resell it.

Where is the list of what is missing?

  • A quote with no exclusions was never costed. Ours sits on this page and names key recovery, payments, enterprise sign-on, the hardening pass and more, so nothing turns up later.

The Six-Step Delivery Process

What happens after you say yes, in order.

Choose sign-in, start the slow queues

  • You decide between phone codes, email and social sign-in. Phone codes cost money on every signup in most markets, and in some places the number is the identity people expect. Your side also files for developer accounts and SMS sender registration on the same day, because those approvals set the calendar.

Your brand across all four surfaces

  • Name, colors, logos, favicon, banner, copyright and store links are applied to the iPhone and Android apps, the browser client and the console, together with the languages you enable. Later changes are console forms and need no release.

Write the rules of your community

  • Report reasons for people and for groups, a group size limit, wallpapers, default avatars and alert sounds. Operator logins are created separately from every member account, on a tier of their own.

Walk it end to end, then hand over

  • Two devices carry a conversation through photos, a voice note, a group with a second admin, a video call and a story. Then a report is filed and taken through the queue to a block, which is the path most demonstrations avoid.

A support window with a name on it

  • A named engineer stays through handover. We also size the first deployment with you and record which measurement should trigger which scaling step, so the growth plan is held by your team.
  • Day zero deserves the most attention. A finished platform without an approved developer account or SMS sender is still an app that cannot reach members, and no provider can shorten someone else's review.

Red Flags That Mean Walk Away

Five claims that should end a sales call

  • "You get a license, the code stays with us." Then every change you want becomes a favor you have to request. An app you cannot alter is a rented storefront wearing your logo.
  • "Conversations are stored on our servers." Identities, messages and media are what you are building. Find out where they live and how you would get them out before you enrol a single member.
  • "Encryption is available as an upgrade." Ask what the quote becomes. A price that holds only while conversations are readable is an opening position, not a price.
  • Press hardest on the first, since it is the most tempting. Cheap access to code you cannot change feels like a saving and behaves like a lease.

What a Messaging Platform Has to Get Right

The unglamorous parts that never make a screenshot and decide whether the platform still works a year in.

What We Have Not Done Yet

Six limits, put in front of you before the purchase and not after it.

No payment processing or subscription billing

  • Not part of an initial scope, since a messenger works without either and the right provider depends on your market. Charging for access is an integration against your own merchant accounts, quoted on its own.

Four items you grow into

  • A real-time adapter across several servers, media on object storage with signed URLs and a CDN, append-only audit logs forwarded to a SIEM, and outbound webhooks for bots. The groundwork for the first two is already in the build. There is no certificate here: the VAPT compliance document is a reference for your testers.

What is built is real, what is around it is yours

  • Four surfaces, encrypted chat, WebRTC calling with relay fallback, twelve message types, stories with true expiry, both moderation queues and sixteen languages. Your members, contacts, retention duties, lawful-access obligations, SMS sender registration and local privacy and telecoms law are not supplied and are your responsibility.
  • This is an original implementation on Node.js, Flutter and React. No messaging brand is a supplier, partner or reference customer of it, and none is implied anywhere on this page.

Modelled Reference Deployment

An illustration, not a client story. It shows how the platform would be arranged for a software agency that redeploys one build for several customers. Each number describes the build and none reports a result.

An Agency Running One Build for Several Customers

  • A regional software agency whose customers each want a private messenger with their own name, language and moderation rules, and who would rather run one codebase than maintain a fork per customer.
  • The situation: every customer wants its own look, its own languages and its own report reasons, and a rented platform would put the agency's whole client list on another company's terms and billing.
  • The configuration: a separate deployment for each customer on servers of that customer's choosing, rebranded from the console, with sign-in methods, languages, group limits and integration keys set per brand. The agency bills its own relationship and nothing flows back to us.
  • What is already in an initial scope: iPhone, Android, browser and operator console, end-to-end encrypted chat, device-to-device calls, both moderation queues, and branding a non-technical operator can change. Payments, single sign-on and the hardening pass remain scoped work per customer.

Choose on the answers, not the pitch

Message between the two live accounts, then ask us to file a report and work it through the queue. The first proves the product and the second proves the platform.

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by WhatsApp , or any other messaging, chat or calling service.

Discuss this scope by message

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com