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

Choosing a Bolt.new 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 discussion by message

  • Agree providers, plan structure, data permissions, credit rules and acceptance checks by message before provisioning.

Deployment on your infrastructure

  • Scope approved hosting, migrations, authentication proxy, credential handling and transport/environment controls; validate the selected deployment.

Plan and provider configuration

  • Define input/output pricing metadata, model access and feature flags with versioned review and rollback.

QA and handover

  • Test builder, selected plan and admin flows against written checks, then hand over agreed source, deployment evidence, documentation and unresolved issues.
03 / What to Check

What to Check Before You Hire

Ask every bidder, including Omnistu, for written answers and evidence for the same requirements. Unanswered questions remain diligence gaps, not proof of a particular vendor outcome.

Where does generated code execute?

  • Ask where code, installation and previews execute, and request measured compatibility, isolation and operating-cost assumptions for each option.

Who holds the provider keys?

  • Ask where provider credentials are stored and injected; require tests of browser bundles, responses, errors and logs rather than accept an architectural assurance.

Can I change plan economics without a deploy?

  • Ask which plan, model and pricing changes are configuration versus code, who approves them, and how either kind is tested, audited and rolled back.

Do I receive the source code, in writing?

  • Get source access, ownership, third-party licences, generated-code handling and handover obligations in writing; platform access alone does not settle source rights.

How many providers, really?

  • Request the actual supported-provider list and adapter tests; ask whether an additional provider needs configuration, engineering or a new agreement.
04 / A proposed launch process

A proposed launch process, without time promises

Define the first builder workflow

  • Define the initial audience, permitted tasks, supported runtime, data categories and provider/model inventory.

Apply your branding

  • Apply the approved name, logo, colours and theme to agreed builder, account and admin surfaces; confirm third-party attribution requirements.

Set the commercial rules

  • Agree plans, seats, credits, usage pricing, spending limits, taxes, refunds and team attribution without assuming a checkout already exists.

Connect your own accounts

  • Connect approved model, repository, hosting, payment and notification accounts with scoped permissions and separate confirmation for external writes or spending.
05 / Red Flags That Mean

Red Flags That Mean Walk Away

Review technical, economic, contractual and operational gaps together. Request evidence, exclusions and named owners before choosing a supplier.

06 / What a Generative Developer

What a Generative Developer Tool Has to Get Right

Execution boundary and cost review

  • Evaluate browser-side versus hosted execution through compatibility, isolation, data-flow and cost tests; neither option guarantees flat cost or removes the security boundary.

Metering that matches reality

  • Reconcile provider-reported input/output usage, estimates, final accounting and corrections, including timeout and cancellation cases.

Per-model economics

  • Scope credit rules per provider, model and plan with current pricing metadata and explicit cost limits.

A ledger you can point at

  • Record grants, usage, bonuses, corrections and refunds with reasons, references and authorized actors; retain a reviewable dispute path.

First-session template validation

  • Test first-session templates, dependencies, preview failures and incomplete generated output against the intended beginner workflow.

A way out

  • Scope source export, repository push and hosting deployment separately; verify destination, permissions and approval before an external action.
07 / Platform Trust & Code

Platform Trust & Code Custody

A code-custody review should map where project files, prompts, generated code, credentials and logs travel, who can access them, and how the proposed boundaries will be tested.

Code custody and data flow

  • Document where source, prompts, generated code, logs and provider requests travel. A browser runtime does not prove that no third party receives data.

Access & Spend Control

  • Define plan/model access, team attribution, an append-only usage ledger and reconciliation against real provider records.

Deployment Hardening

  • Configure and test transport security, browser headers, environment secrets and network policy for the actual hosting environment and approved data flow.
  • Record selected capabilities as proposed, implemented, configured and verified only when the corresponding evidence exists; no readiness label substitutes for acceptance.
Scope and evidence

Checks before accepting this part of the build

Proposed acceptance questions for this page. They do not imply a completed product, active integration, measured benchmark or approved spending.

Inspect evidence, not labels
  • Ask for a demonstration with approved test data and inspect generation, permissions, metering, errors and deployment approval.
  • Request the supported-provider inventory and actual test conditions before accepting capacity, security or readiness assertions.
Clarify custody and ownership
  • Map code, prompts, provider requests, logs, keys and project exports with account and access owners.
  • Agree source/licence terms, generated-code handling, dependencies, data deletion and third-party runtime obligations in writing.
Agree the acceptance handover
  • Name who can deploy, approve spend, change plans, respond to incidents and run rollback.
  • Receive reviewed source, configuration, runbooks, acceptance results and unresolved issues; verify access without sharing reusable secrets.
09 / 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