PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
Engagement scope - proposed scope

Choosing a HeyGen Clone Development Company

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.

Build scopeConfirm servicesDefine the features and exclusions
Delivery planAgree milestonesNo fixed launch duration implied
Source rightsWritten termsCheck licences and handover
OperationsTest before launchAgree acceptance and support
01 / Scope areas

Scope areas for this kind of build

The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.

02 / Development Process

Development Process

Scope call

  • Languages live at launch, plan structure, which providers you intend to use, and whether you are selling to teams or to enterprises.

Plan and workspace configuration

  • Generation and export entitlements per plan, API metering, role definitions and a seeded template library so a new workspace is productive immediately.

QA and handover

  • Functional pass across user, creator, manager and the admin command center, then handover of the running platform with full source code and documentation.
03 / What to Check

What to Check Before You Hire

Is tenancy real, or a filter?

  • Ask whether every project, asset, template, webhook and subscription hangs off a workspace. Tenancy retrofitted as a query filter leaks, and it leaks in front of a customer.

What happens under load?

  • Campaign weeks are spiky. Ask what the queue does when a hundred renders arrive at once, and whether there is a fallback path when workers saturate.

Is translation a re-render?

  • If localization simply regenerates the video, a failed translation costs you the original too. Ask whether it is a separate job with its own status and retry.

Can I enforce limits per plan?

  • On a product with per-minute provider cost, generation and export entitlements must be enforced by the platform. If they are honour-system, your margin is a hope.

Show me the audit trail

  • Ask what a security reviewer sees. Who generated what, in which workspace, when. This is the question that decides enterprise deals.

Do I receive the source code?

  • "You own your platform" and "you own the code" are different sentences. Get the second in writing, especially when client scripts pass through it.
04 / A proposed launch process

A proposed launch process, without time promises

Define the first service area

  • Where you operate, what you charge inside it, and any limits such as cash-on-delivery ceilings. The first zone usually becomes the template for the ones that follow.

Apply your branding

  • Name, logo, colour scheme and invoice layout applied across the storefront and apps. Which parts are configuration and which are build work is confirmed in the written scope.

Set the commercial rules

  • Commission or subscription structure, discount responsibilities, delivery pricing per zone, tax rules and payout preferences, recorded in the written scope.

Connect your own accounts

  • Payment gateways, store listings, maps and notification services stay under your own accounts, with access arranged before build work starts.
05 / Red Flags That Mean

Red Flags That Mean Walk Away

We would rather you use this list on us than skip it. On a multi-tenant generation product the failures are quiet until they are severe.

06 / Platform Trust & Content

Platform Trust & Content Governance

Marketing teams put unreleased campaigns and brand assets into this platform. What a security review asks is who can see them, who did what, and where it all runs.

Workspace Isolation

  • Every project, asset, template, webhook and subscription belongs to a workspace. One deployment serves multiple brand teams or clients with each seeing only its own content, which is what makes agency and multi-brand operation defensible rather than merely possible.

Audit Trail

  • The proposed admin command center would carry deployment-wide audit logs alongside sessions, users, projects and assets. It is the surface that would answer a procurement questionnaire - enterprise review typically asks for exactly this audit trail.

Role & Access Control

  • User, creator, manager and platform admin are distinct surfaces rather than one interface with buttons hidden. API keys would be issued and revoked at workspace level, with per-endpoint usage metering behind them.

Deployment Control

  • The platform runs on your infrastructure, so transport security, security headers, secrets handling and data residency are configured to your organization's standard at deployment rather than inherited from a vendor's shared tenancy.
  • Readiness is stated per capability as included, configuration required or integration required, so nothing surprises you after purchase.
08 / Next step

Discuss your scope by message

Tell us what you want to launch and where. We reply by email with a scoped proposal - no calls required, no phone numbers collected.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead