Product development / SaaS Development
A SaaS product with clear tenancy, billing and operating rules.
Plan the customer workspace, tenant admin and platform operation together. Make access, usage, subscriptions and receiving-team handover explicit before choosing an existing base or a custom build.
Discuss your project โContents ยท SaaS Development
Define the operating product before selecting a base.
Start with the paid workflow
A subscription product needs more than sign-up and a checkout. Identify the recurring job, the users who do it and the permissions, data and integrations it requires. Then define the workspace, tenant administration and platform operation needed to run that job. A reusable base is an option to inspect, not proof that the product or market is ready.
Choose a base or custom scope
Website creation, campaigns, file storage, meetings and property operations have different domain models. Compare an actual proposed implementation with the required workflow and the future team's skills. A new workflow, enterprise identity requirement or dedicated data boundary can change the architecture rather than fit as a branding adjustment.
Make the operating contract explicit
Record tenancy, subscriptions, metering, plan limits, customer exit and operational responsibilities alongside the screens. Require testable acceptance for sign-up, tenant switch, invitation, upgrade, failed payment and cancellation. Keep engineering claims separate from regulatory attestation, provider eligibility and customer demand.
Six startup decisions to make explicit.
Tenant separation
Choose shared tables, separate schemas, separate databases or dedicated infrastructure from the actual threat model, operating needs, data location and customer obligations. Bind tenant selection to server-verified identity and current membership; an opaque identifier is not access control.
Billing model
Define seats, usage, tiers, trials and any hybrid rules. Specify billable events, units, rounding, credits, limits and corrections before collecting usage. Decide how late events and plan changes affect invoices and entitlement.
Roles and permissions
Model users, team membership, tenant owners and platform operators as separate responsibilities. Authorize each resource and action on the server, including exports, files, jobs and administrative access.
Onboarding
Map signup or invitation through workspace creation, identity verification, configuration and the first useful workflow. Handle expired invitations, duplicate accounts, failed setup and the user who needs help rather than treating account creation as product adoption.
Quotas and resource protection
Define rate limits, per-tenant quotas, queue fairness and resource budgets. Test limits across API, storage and background jobs so one tenant cannot silently consume another tenant's capacity.
Export and deletion
Specify authorized data export, retention, deletion, backups and offboarding. Define related records, legal retention exceptions and revocation of account and service access. Test the full operation, not only a visible button.
Six product concepts and their distinct requirements.
These are planning concepts, not verified available bases, client deliveries or affiliations with other products. Inspect current source, rights, dependencies and working coverage before relying on reuse.
Website builder
Templates, editing, assets, publishing, custom domains and hosting require ownership and tenant-isolation boundaries.
Email campaigns
Contacts, consent, templates, schedules, delivery, unsubscribe and suppression rules need provider eligibility and lawful sending behavior.
File storage
Uploads, folders, sharing, retention, quotas and download permissions need safe object access and malware/abuse review.
Video meetings
Rooms, invitations, media permissions, participant roles, recording and connectivity recovery need explicit service and content rules.
File transfer
Large uploads, resumable transfer, recipient access, expiry and deletion need clear storage and recovery policies.
Property operations
Tenant portals, leases, maintenance and rent records need role separation, financial accuracy and auditable changes.
Three connected surfaces with different authority.
Scope the following capabilities individually. This inventory preserves the original product breadth as requirements to inspect and agree, not a claim that a working base, app, backend or service is currently included or available.
Customer workspace
The user performs the product's actual work with permitted records and features. Branding, domain and team context must not allow access to another tenant. Include accessible loading, empty, stale, denied and failure states.
- Role-based dashboard access. Define which records and actions each role may access, and enforce those checks on the server.
- Team invitations and permission management. Scope who can invite, accept, remove or change members, including expired links and revoked membership.
- Notifications and activity feed. Define event recipients, private-data content, freshness, read state and recovery when delivery is delayed or unavailable.
- Workspace search. Authorize search results and snippets by current tenant and membership, including saved filters and index updates.
- File upload and version history. Scope file type/size, malware and abuse handling, object access, history, retention and restoration.
- Integration connections. List supported integrations, account consent, credentials, scopes, disconnect behavior and failure/retry contracts.
- Billing and plan changes in the product. Define eligible checkout, upgrade/downgrade, proration and entitlement behavior with the selected provider and distribution rules.
- Developer API-key self-service. Define credential creation, restricted scopes, one-time display where appropriate, storage, rotation, revocation, quotas and audit.
- Data and audit-log export. Authorize export creation and download, restrict private data and define format, retention and deletion of generated files.
- Multiple interface languages. Scope supported locales, translation ownership, date/number formatting and layout including right-to-left where required.
- Dark mode and accessibility. Test contrast, focus, keyboard, screen-reader and text-scaling behavior in each supported appearance.
- Responsive browser access. Define desktop, tablet and phone layouts and browsers as actual test targets rather than infer them from a shared codebase.
- Enterprise SSO/SAML. Scope identity-provider metadata, tenant/domain mapping, account linking, provisioning, revocation and administrator recovery separately.
- In-product support chat. Identify the support service and staff responsibility, consent/data flows, operating hours, escalation and unavailable-service behavior.
- Tenant-specific branding. Scope permitted logos, colors and assets with ownership and upload controls; branding is not tenant data isolation.
Tenant admin
Scope invites, seats, roles, usage, plans, billing self-service and custom domains. Restrict sensitive changes, verify domain ownership and retain appropriate audit history.
- Workspace settings and branding. Authorize configuration changes, validate assets and domains, audit sensitive edits and define recovery.
- User seats. Distinguish invited, accepted, active and billable seats and define removals, over-limit behavior and billing changes.
- Usage metering and quotas. Specify units and event identity, delayed/duplicate corrections, enforcement and visible measurement freshness.
- Webhooks and automation rules. Define authorized destinations, signatures, event schemas, safe secrets, retries, deduplication, rate limits and audit.
- Custom domains. Verify ownership, TLS, routing and offboarding, including stale/reassigned domains and cross-tenant configuration errors.
- Invoices and payment-method updates. Use supported provider flows with authorized billing roles; distinguish a requested update from confirmed provider state.
- Security policies. Define available controls, role authority and enforcement for sessions, identity, access and sensitive operations.
- Retention preferences. Map configurable retention to records, files, exports and backups, including legal exceptions and deletion verification.
- Sandbox and production environments. Separate credentials, data, events and provider accounts so test activity cannot change real customer or financial state.
- Administrative audit log. Record appropriate actor, action, target and time with restricted access, integrity, retention and privacy controls.
- Role templates. Define template creation and assignment, explicit permission changes, versioning and review of existing users.
- Bulk user import. Specify the CSV schema, validation, duplicate handling, previews, authorization, error reporting and rollback/recovery.
- API usage reports. Show approved metrics with source, time window, measurement lag and tenant boundary; avoid exposing secrets or sensitive payloads.
- Compliance-review exports. Define the requested evidence and authorized recipients with legal/audit review. An export pack is not an attestation or compliance certificate.
- Priority support escalation. Agree the actual route, severity, coverage, response versus repair target and charges in writing; a button does not supply a staffed service.
Platform admin
Scope tenant provisioning, provider configuration, operational diagnostics and authorized support actions. Use least privilege, auditable access and deliberate data minimization rather than a universal operator bypass.
- Tenant provisioning and suspension. Authorize creation, changes and suspension with audit, data preservation and a defined recovery/offboarding path.
- Subscription-plan configuration. Version tier, price, seat, usage, trial and entitlement rules and verify how changes affect existing customers.
- Platform feature flags. Scope who can change flags, their tenant/user targeting, safe defaults, audit and rollback.
- Revenue and recurring-revenue reports. Define recognized versus provisional figures, adjustments, currency and reporting windows from authoritative financial records.
- Churn and cohort reports. Write the cohort and churn definitions, denominators, observation window and data lag rather than present unexplained charts.
- System health and uptime monitoring. Specify checks, endpoints, measurement limits, alert owners and incident response; a chart is not an uptime commitment.
- Support-ticket routing. Define queues, access, assignment, escalation, retention and handling of private customer information.
- Dunning and payment retries. Use eligible provider behavior and explicit customer rules for reminders, retry, grace, suspension and recovery, with verified events.
- Reseller/partner management. Scope partner authorization, tenant boundaries, branding and licence/financial arrangements in the actual contract.
- Data residency by region. Identify all application, backup, log, object and provider data locations and access. Dedicated regions or instances require explicit custom scope and verification.
- Privacy-program controls. Specify access, retention, export/deletion and evidence controls appropriate to the program. SOC 2 and privacy-law obligations are not established by software settings.
- Email and in-app campaigns. Define consent, suppression, unsubscribe, authorized audiences, provider eligibility and diagnostic privacy.
- Rate limits and abuse controls. Set per-user/tenant/API budgets, enforcement, review and recovery with meaningful tests; limits do not guarantee abuse prevention.
- Ecosystem revenue-share rules. Verify eligible transactions, counterparties, provider arrangement, fees, refunds, disputes and reconciliation before implementing any distribution.
- Platform API governance. Document clients, scopes, schemas, versions, lifecycle, quotas, audit and deprecation/support responsibility.
Choose the build route against the operating requirements.
On smaller screens, scroll the table sideways to read every column.
| Decision | Existing SaaS base | Custom product | Hosted white-label service |
|---|---|---|---|
| Starting point | Inspect its actual workflow and dependencies. | Design around a documented workflow and data model. | Inspect the provider's available configuration and service. |
| Scope and milestones | Measure the gaps, branding, migration and integrations. | Plan delivery against accepted features and controls. | Check onboarding, configuration and provider constraints. |
| Cost structure | Quote the actual base licence and additional work. | Itemize engineering, operation and maintenance. | Review recurring, seat, usage and exit charges. |
| Source and rights | Verify transfer and reusable-component terms. | Assign custom work and identify third-party licences. | Verify export, API and migration rights; source may be unavailable. |
| Tenant control | Test the implemented tenancy and chosen hosting. | Choose isolation, location and operation for the requirements. | Review the provider's data access, regions and contract. |
| Fit | Where verified coverage matches the intended workflow. | Where distinctive rules or operating boundaries need new work. | Where the service and its constraints fit the operating plan. |
Five questions to settle before implementation.
Which SaaS concept is the right starting point?
Map the paying user's job first. Website and template builders need publishing and custom domains; campaigns need consent and delivery; file products need object permissions and retention; meetings need media and recording rules; property tools need leases, maintenance and financial records. Inspect the relevant implementation rather than treating a well-known product name as evidence of equivalent features.
What is included in the launch quote?
List the end-user workspace, tenant admin, platform admin, billing, configuration and release outputs individually. Separate enterprise identity, dedicated hosting, migration, integrations and custom workflows. List hosting, storage, email/SMS, payment, AI and video usage as continuing provider costs with explicit account ownership.
What should the customer prepare?
Bring the product name and permitted brand assets, domain/cloud access, data and role definitions, plan names, units, limits, trials and cancellation rules. Verify the chosen billing account and eligible operating region. If mobile apps are required, establish developer accounts and submission prerequisites. Share credentials securely, not in a project brief.
Who owns compliance and data-residency decisions?
Map the seller's legal role, customer contracts, retention, subprocessors, access and storage regions. Specify technical controls and acceptance evidence, with appropriate legal and audit review. Tenant isolation and an audit log are useful controls, not a SOC 2 report, a privacy-law conclusion or blanket regulatory compliance. A dedicated instance still needs correct configuration and access.
How should a reference project be evaluated?
Ask for permissioned, dated evidence showing the actual product, the supplier's role, reusable versus new work, the delivered interfaces and independent operation. No named customer, delivery count, timeline or commercial outcome is established by the examples on this page. Use the project-pattern requirements below to assess a relevant demonstration.
Five transaction stages and the important branches.
Signup or invitation
Verify identity and invitation scope, create or join the correct workspace and assign the permitted role. Define duplicate, expired and partially completed setup recovery.
Core workflow
Let the authorized user perform the job the product exists for. Keep product state distinct from billing status and show actionable permission or provider failures.
Usage and limits
Record defined billable events with tenant and event identity. Reconcile duplicates, delayed records and corrections. Enforce the agreed quotas without assuming a dashboard counter is authoritative.
Subscription cycle
Apply the selected plan and provider-confirmed subscription state. Handle trial end, renewal, changes, failed payment, invoice and dunning behavior with verified and deduplicated events.
Operational reporting
Define the source, time window and denominator for usage, churn or recurring-revenue reports. Separate provisional and reconciled figures and restrict tenant/platform reporting access.
Trial and checkout
Agree trial eligibility, end conditions and provider checkout. A browser return is not proof that payment succeeded.
Seat provisioning
Apply accepted membership and entitlement rules, including invitation, removal, downgrade and over-limit behavior.
Usage feedback
Show measured usage with freshness and remaining-limit context. Make correction and reconciliation visible when records arrive late.
Six commercial models to define and verify.
Per-seat subscriptions
Define who counts as a billable seat, invitations versus accepted members, billing periods and seat-change adjustments.
Usage-based billing
Specify the measured unit, event identity, aggregation, rounding, limits and corrections. Keep metering and invoice reconciliation testable.
Enterprise contracts
Scope negotiated terms, SSO, dedicated infrastructure, support and service obligations only where actually agreed.
Ecosystem transactions
If third-party apps or services are sold, define eligible provider arrangements, platform fees, entitlement and disputes.
Professional services
Separate onboarding, migration and custom integration work with its own deliverables and acceptance.
White-label licensing
Define permitted branding, redistribution, hosting and source rights, tenant operation and support responsibilities in the licence.
Model revenue from explicit assumptions about eligible users or transactions, fee basis, refunds and operating costs. Keep forecasts separate from observed results; no earnings or demand is promised.
Different operators bring different requirements.
Vertical product teams
Map an industry-specific workflow to the required roles, data, integrations and customer obligations. Choose reusable components only after inspecting their real coverage.
Agencies
Separate each client's workspace, data, branding and access. Agree who sells, operates and supports the service and which rights allow redistribution.
Existing operators
Review whether an internal tool is suitable for external customers. Add appropriate tenant boundaries, onboarding, billing, support and customer data exit.
Investors and venture teams
Validate the product and operating assumptions against an actual target customer and permitted evidence. Source ownership, a prototype or a subscription screen is not proof of demand or investment return.
Five supplier questions to put in writing.
Current scope and quote
Compare the inspected base, missing work, integrations, receiving and ongoing costs in an itemized written quote. Do not assume a catalogue label fixes the effort.
Rights and accounts
Confirm custom and reusable source rights, third-party licences, cloud and domain ownership, provider roles and an executable exit plan.
Admin coverage
List customer, tenant and platform-admin outputs and permissions. Identify provisioning, plan configuration, billing and support operations that are included or separate.
Representative QA
Inspect browser/device and API behavior for expired sessions, duplicate billing events, tenant switches, upgrades and denied actions. Screenshots alone are insufficient.
Milestones and dependencies
Set acceptance and milestones around the actual work, with provider verification, customer prerequisites and external review kept distinct.
Four boundaries to implement and test.
Workspace interfaces
Select web/mobile surfaces, rendering and state lifetimes. Keep per-request identity and private data isolated and test account/tenant switches.
Tenant operations
Version seat, role, plan, domain and quota changes with appropriate audit and recovery. Domain branding does not itself establish tenant isolation.
API and background work
Carry verified tenant context through resources, database, cache, object storage, queues, jobs and exports. Reject unauthorized cross-tenant identifiers and test both allowed and denied paths.
Billing and entitlements
Keep provider payment/subscription state, metering, plan rules and feature access consistent through verified events and reconciliation. Account for delayed, duplicated, missing and out-of-order notifications.
Select the stack and inspect the actual implementation.
Clients and application language
Flutter and Dart are possible shared-client choices; browser-specific frameworks or native apps may fit different requirements. Verify supported platform versions, accessibility, rendering, app size and receiving-team skills. Do not infer an included mobile app from a SaaS label.
API and business services
Laravel or Node.js can support application APIs, with explicit contracts, authorization and background jobs. Version the tenant and plan model, validate inputs and keep server secrets out of client applications.
Identity, messages and live state
If Firebase authentication, FCM, Firestore, WebSockets or Twilio are selected, document each service's role, credentials, region, quotas and data access. Provider authentication does not replace application authorization or tenant checks.
Data and asynchronous work
MySQL may hold transactional records, Redis may serve cache or queues, and SQLite/Hive may cache local data. Specify ownership, schema changes, backup, consistency and expiry. A local database is not automatically an encrypted or safe offline synchronization solution.
Billing and location integrations
Stripe or Razorpay eligibility, subscription behavior and account responsibilities need current provider verification. Google Maps or Mapbox should be included only when location is part of the workflow, with appropriate terms, keys and cost limits.
Build and operation
Codemagic, Docker/AWS and Sentry are possible build, hosting and diagnostics tools. Test repeatable releases, secure configuration, redaction, alert routing and restore procedures. A tool selection is not proof that a pipeline or monitoring response has been implemented.
Quality requirements specific to this operating model.
Tenant and membership boundaries
Exercise the same resource as owner, member, removed member, other tenant and platform operator. Include direct API requests, search, files, exports and jobs. Verify current membership and cache handling after a tenant switch, not only initial sign-in.
Billing and entitlement recovery
Test trial end, plan and seat changes, failed and delayed payment, duplicate/out-of-order events, cancellation, refunds and reconciliation. Keep a provider event, invoice state and feature entitlement distinct until the implemented rules connect them.
Realistic workspace use
Use populated lists, reports and tenant configurations with keyboard and assistive-technology checks. Test data export/deletion, invitation expiry, domain verification and resource quotas. Define support access and its audit trail before using real customer data.
Six release and receiving-team checkpoints.
Review and change control
Require traceable review of application, API, configuration and migration changes. Inspect authorization, business rules, dependencies and error handling together. Agree which checks block merge and how an exception is approved and recorded.
Automated and end-to-end tests
Cover domain rules, data boundaries and the critical user paths with unit, integration and end-to-end tests. Include denied actions, retries, expired sessions and partial failures. Set meaningful coverage and acceptance criteria for the actual scope rather than treating a percentage as proof.
Release-build performance
Measure the production configuration with representative devices, browsers, network conditions and realistic data. Record cold and repeat loads, slow operations and resource use against written budgets. Keep the observations and unresolved limitations with the release.
Security and privacy
Check server-side authorization, secret handling, dependencies, logging and the exposed attack surface. Keep private data out of client bundles, analytics and diagnostics. An automated scan or encryption setting is not a complete security assessment or a compliance certificate.
Release and recovery
Rehearse deployment, schema changes, backup restoration and rollback. Verify the domain, TLS, environment settings and provider configuration. For mobile scope, inspect signing, privacy disclosures and store-submission responsibilities without promising approval.
Handover and operation
Test the receiving team's access, build and recovery instructions. Verify monitoring, alert routing, support terms and the defect register. Record accepted limitations and follow-up owners before calling the release accepted.
Five stages from scope to independent operation.
Brief and confidentiality
Describe users, the core workflow, existing systems, sensitive data and business constraints. Agree confidentiality and information-sharing boundaries before handing over restricted material.
Scope and plan
Choose the build route and inspect any proposed existing base. Write the role matrix, architecture, integration contracts, exclusions, acceptance tests, dependencies and milestone plan with an itemized quote.
Build and review
Use version control, repeatable environments and checks suitable for the project. Review working increments against the agreed workflow, including loading, empty, denied and failure states. Track scope changes explicitly.
QA and release decision
Run the agreed functional, integration, accessibility, security and performance checks against the release build. Rehearse migration and recovery, preserve evidence and decide which issues block launch.
Launch and handover
Release through authorized accounts with a tested recovery path. Deliver source, documents and operating access, confirm monitoring and support ownership, and have the receiving team demonstrate the essential operations.
Write down the build, dependencies and continuing costs.
Build scope
Count the user roles, permissions, workflows, client surfaces and admin operations. Identify where an inspected existing component actually fits and which gaps need new work. Price the agreed outputs rather than a catalogue label.
Integrations and data
Itemize provider onboarding, external-system contracts, legacy migration, data quality, reconciliation, media, messages and real-time work. Include test environments and provider restrictions, not only a connection button.
Non-functional requirements
Document accessibility, device/browser coverage, traffic and latency targets, resilience, retention and data location. Regulatory and security obligations need defined controls and review; they are not automatic properties of a framework.
Operation and ongoing costs
List hosting, database, storage, bandwidth, payment fees, maps, email/SMS, monitoring and any AI or video usage separately from engineering. Include maintenance, backups and support, plus who owns and pays each account.
Commercial terms
Request a current itemized written quote, acceptance-linked milestones and a change process. Confirm taxes, recurring charges, cancellation and rights. No price, duration, included support window or service level is established by this page.
An illustrative project pattern, not a client result.
Meeting-platform requirements
A conferencing product can require rooms, invitations, participant roles, signalling, media transport, connectivity recovery, recording and moderator tools. Specify the media provider or service boundaries, permissions, retention and participant notification. These are example requirements, not a record of a delivered client project.
Reuse and custom work
Inspect any existing meeting base and document exactly what is reusable, licensed, changed or missing. Compare its role, billing and tenant model to the intended business. A screenshot or a claim about reused building blocks does not establish production behavior or source rights.
Acceptance and receiving
Demonstrate representative calls, permission denial, disconnect/rejoin, recording controls, tenant isolation and subscription changes. Deliver the code and operating notes actually in scope and have the receiving team run them with authorized accounts. No delivery duration, customer count or revenue result is implied.
Evaluate relevant references and actual product evidence.
Ask for dated, permissioned references and establish the supplier's actual role, delivered scope and receiving-team operation. Inspect the implemented workflow, access control and exceptions rather than treat a quote, star rating or catalogue entry as proof. No named customer, review score, award or launch outcome is asserted here.
Check the supplier and the work you will receive.
Legal identity and contract
Verify the contracting entity and authorized signatory against current official records. Match the entity on the scope, invoice and rights agreement. Do not infer registration, history or financial standing from a website badge.
Evidence behind claims
Ask for dated, permissioned evidence behind project counts, app launches, outcome figures and technical claims. Check what was actually delivered, what belonged to an existing component and what remains a prototype or proposed scope.
Independent reviews
Open current review records and inspect author, project scope, date and platform verification. Treat ratings as context rather than a substitute for source, acceptance and receiving-team checks.
Relevant product inspection
Request access to the actual version proposed for the project, with safe test data and agreed permissions. Walk through the required role paths and failure states. A screenshot, catalogue name or attractive landing page does not establish a working backend.
Permissioned references
Where a past project matters, ask for a reference and permission to discuss it. Establish the supplier's role, delivery boundaries and current operator without republishing private customer information.
Named responsibilities
Ask who owns engineering decisions, QA, release approval and support. Record backups for unavailable contacts and how changes and unresolved risks will be reported. Do not substitute stock biographies or unverifiable team claims.
Related scopes for a connected product.
Agree rights, changes, handover and support.
Written scope
Describe included workflows, roles, interfaces, integrations, data and acceptance evidence. Record exclusions and assumptions so a feature name cannot stand in for an implementation contract.
Source, licences and accounts
Put the custom-code assignment, reusable-component licence and third-party restrictions in the contract. Identify every app, API, admin console, migration, infrastructure script and design asset being delivered. Keep cloud, domain, billing and developer-account ownership explicit. A source archive alone does not establish unrestricted rights or an independent release path.
Dependencies and changes
List customer inputs, provider approvals and third-party limits. Track changes with their scope, cost and milestone impact before proceeding. Separate engineering completion from app review, payment eligibility and the decision to open to customers.
Support and ongoing work
Agree the support start event, duration, working hours, contact route, severity definitions and response versus repair commitments in writing. Separate defects against accepted scope from new features, provider changes, security maintenance and operating work. Monitoring needs a named responder and an escalation route; a dashboard alone is not support.
Receiving-team handover
Require repository history, a dependency and licence inventory, setup instructions, API contracts, database migrations, environment-variable names, deployment and rollback steps, and an operating runbook. Transfer secrets through a secure channel rather than source control or a document. Have the receiving team build, restore and release with its own authorized access.
Questions about SaaS Development.
Can Omnistu deploy a multi-tenant SaaS app from a clone base?
An inspected base may be suitable, but first verify its customer workspace, tenant admin, platform console, membership model, metering and billing. Document any missing features and test tenant isolation and provider-event recovery. The presence of a base is not proof of a deployable, complete SaaS product.
How quickly can a B2B SaaS MVP launch?
Set milestones after inspecting the scope, repository and provider dependencies. Distinguish build and acceptance from developer-account verification, payment onboarding and app-store review. Do not use a catalogue turnaround as the delivery promise for a custom product.
What monetization models are supported out of the box?
Possible models include seats, measured usage, tiers, trials, enterprise contracts and a defined mix. Confirm which are implemented in the proposed version. Define billable units and events, corrections, failed-payment behavior and quota enforcement; do not assume dunning, SSO or metering is preconfigured.
Do tenants get isolated data and branding?
Branding and domain mapping are different from data isolation. Authorize tenant membership and each resource on the server, propagate verified context through cache, jobs, storage and exports, and test cross-tenant denial. Dedicated instances, regions and custom domains need explicit scope and operating controls.
Is the SaaS source code included?
Require the full delivery inventory and rights terms in writing: custom code assignment, licences for reusable and third-party parts, source history, API and migration documents, build and release scripts, and authorized account access. Have the receiving team reproduce a release. Do not assume ownership or absence of future licence fees from a source-code promise alone.
Can Omnistu integrate SSO and SAML for enterprise clients?
Scope the required identity protocols, provider, domains, metadata, role mapping, provisioning, revocation and recovery. Test invitation and account linking, tenant membership, session expiry and the fallback administrator. No enterprise SSO or standard sign-in package is assumed to be included without inspection.
What does the published SaaS price cover?
The amount depends on the accepted scope and the inspected starting point. Request an itemized current quote covering roles, workflows, integrations, data, QA, release and handover, with provider charges and continuing operation separate. This page does not establish a fixed price or an automatic package inclusion.
What post-launch support is included for SaaS products?
Confirm the actual support window and start event, defect definition, response hours, escalation and charges in the signed terms. The duration mentioned in the question is not verified as an available offer here. Keep new features, provider changes and continuing operations separate from in-scope defect repair.
Does Omnistu handle App Store and Google Play submission?
For a product with mobile apps, scope account ownership, signing, provisioning, screenshots, listing and privacy answers, test accounts and review coordination. Verify any payment and account-deletion requirements against current store rules. Submission does not guarantee approval or determine review time; state responsibility for rejections and follow-up.
How is a Omnistu vertical deployment different from hiring a freelance developer?
Compare the actual delivery proposal, not the supplier category. Any supplier may use existing components or build custom work. Look for a named owner, reviewed architecture, source and licence terms, acceptance evidence, secure accounts, release recovery and an executable handover. A company label is not proof of better quality or a faster result.
Which Omnistu client runs a SaaS product on one of these bases?
No named SaaS customer or launch outcome has been independently established for this page. Ask for a permissioned reference and inspect the dated project record, implemented scope and supplier role before relying on a case-study claim.
Where is Omnistu based, and how does a SaaS delivery work?
Start with the written scope, confidentiality, roles, accounts and acceptance plan. Review increments remotely, verify release and handover, and agree support responsibilities. Verify the contracting entity and current contact details directly; no office location or response-time guarantee is established here.
Implementation and platform references.
Use documentation for the selected versions, devices, configuration and operating region. Project acceptance depends on the implementation, not a tool label.
Bring your workflows and operating requirements.
Share the users, business rules, current code and data, integrations, device/browser targets and receiving team. Agree the build boundaries, rights, acceptance evidence and operating responsibilities before implementation.
Discuss your project โ