PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
LinkedIn Clone ยท Development Company ยท Provider Diligence

LinkedIn Clone Development Company: Scope, Evidence and Handover

Compare provider evidence for tier enforcement, profile data, hiring states, outreach credits, CRM failures and moderation records. Request a demonstrated workflow, named exclusions and signed handover terms, not a promise that a profile page and feed establish readiness.

Written questions and answersWeb + Android - recorded scopeNative iOS separate, subject to validation
9Provider questions
6Delivery stages to scope
6Capability groups to test
6Scope limits and dependencies

Original fixed prices, launch/custom-work/support durations, company tenure/project totals, portfolio references, no-callback/no-fee guarantees and categorical provider shortcomings lack verified support here and are excluded. The authored sector scenario below is not a client engagement, capacity test or result. Live-demo readiness is not asserted.

Compare Providers Against Seven Requirements

Compare Providers Against Seven Requirements

The original heading named agencies, freelancers and Omnistu, but its table supplied only freelance and Omnistu columns. Agency questions are added here for a usable three-route comparison, not invented agency facts. No route has a verified speed, price, quality or continuity advantage.

CriterionFreelancer - what to askOmnistu - proposed scopeCustom agency - what to ask
Release readinessWhat exists, what remains, and what dependencies and acceptance tests determine release?Request a demonstration, gap list and signed release conditions; no fixed deadline is verified.What work, staffing, dependencies and acceptance evidence determine release?
Entitlement enforcementWhere are access boundaries checked, and what route/API tests prove it?Five tier states and middleware enforcement are specified; require server-side access tests.How are tiers enforced and tested after pricing or entitlement changes?
Hiring workflowWhich application states, interview and assessment workflows are included?Seven states, interviews and assessments are specified; confirm transitions, permissions and records.Which states, integrations and hiring acceptance tests are contracted?
Moderation and appealsHow are reports, actions, appeals and IP restrictions recorded and reviewed?Separate reports, actions, appeals and IP-ban records are specified; test lifecycle and attributable decisions.What moderation workflows, evidence and appeal controls are included?
Source and rightsWhat code, schema, tests, documentation and rights transfer, under which terms?Next.js/Prisma source and reversible migrations are specified; confirm completeness and rights under signed software/third-party terms.What source, dependencies, documentation and licence restrictions are handed over?
Continuity and exitWho controls infrastructure and accounts, and what happens if support stops?Customer infrastructure and account control are proposed; verify access, backups, export and handover against signed terms.What exit assistance, account control, backups and ongoing dependencies are agreed?
Commercial termsWhat total, exclusions, change process and ongoing charges are signed?Request the current total, exclusions, change approval, software/provider fees and support terms.What quote basis, full cost, exclusions and change controls apply?
Provider Questions

Nine Questions, Answered in Writing

Send these questions to each bidder, including Omnistu. Ask for workflow evidence and contractual answers. No call or consultation is required, and no personal phone number is collected.

01 ยท Where is the tier boundary enforced?

Ask for direct-route and API tests using free and paid accounts. Hidden buttons alone do not prove access control. Verify server-side authorization, data visibility and consistent enforcement after a tier change.

02 ยท Can I reprice without a release?

Ask which prices, allowances and boundaries are configurable, who can change them, and how renewals and existing subscriptions behave. A deployment requirement does not itself prove a bad commercial outcome.

03 ยท What happens to a moderation decision?

Request the moderator identity, reason, timestamp, action history and appeal workflow. Test review and reversal records rather than assuming an email-based process means no trust controls exist.

04 ยท How do I know a CRM push failed?

Inspect delivery logs, failure states, retry policy and monitoring with a controlled failed push. Confirm supported Salesforce/HubSpot account and connector coverage rather than treating an integration-settings screen as evidence.

05 ยท Are certifications verified?

Member-entered certifications are not issuing-body verified in the recorded base scope. Ask who verifies them, by which manual/API process and with what evidence; separate that work from storing a profile field.

06 ยท Are there licence callbacks or code restrictions?

Inspect software terms, encrypted modules, licence-server dependencies, suspension conditions and resale rights. A callback alone does not establish whether resale is legally permitted; confirm the actual signed terms.

07 ยท Who controls provider credentials?

Record ownership and delegated access for payment, email, push and contact-import OAuth accounts. Test export and exit responsibilities. Customer-held accounts do not remove every migration or provider dependency.

08 ยท What has not been demonstrated?

Request a concrete gap list, exclusions, test evidence and separately scoped modules. An incomplete answer needs follow-up, but does not by itself prove dishonesty or lack of product knowledge.

09 ยท What does a data request do?

Inspect request intake, identity checks, approvals, export/deletion execution, retained records and completion evidence. Ask qualified counsel about applicable duties; a manual step is not proof of inevitable failure or noncompliance.

Six Delivery Stages With Explicit Dependencies

Six Delivery Stages With Explicit Dependencies

This is a proposed workflow, not a completion promise or proof the application already works. Dates and deliverables depend on confirmed scope, customer inputs, provider approvals, testing and signed terms.

01 ยท Audience and tier model

Define the audience, buyer needs, five recorded tier states and proposed unlocks. Validate demand and exclusions before commitment; no universal reason for category failure is claimed.

02 ยท Branding across deliverables

List member/company/recruiter/sales web views, operator console, Android build and PWA manifest/icons. The source calls these six surfaces while separately mentioning PWA assets; agree an exact inventory. Native iOS is separate proposed work subject to validation.

03 ยท Infrastructure and accounts

Confirm application/PostgreSQL infrastructure, data rights, approved payment/email/push accounts and contact-import OAuth apps. Define account ownership, delegated access and secure credential handover without requesting secrets in ordinary messages.

04 ยท Entitlements, credits and flags

Specify tier prices, boundaries, outreach-credit allowances and modules/cohorts not being launched. Test server-side access, billing effects and inactive-feature behavior rather than relying on hidden navigation.

05 ยท Trust walkthrough and handover

Create scoped staff roles and test a report through action and appeal with controlled data. List repository/source, schema, migrations, tests, documentation, deployment, backups and access handover; confirm rights under signed terms.

06 ยท Support and custom work

Agree guidance, defect fixes, updates, escalation, exclusions, ownership and charges in writing. Custom modules need their own dependencies, acceptance tests and quote before approval; original launch/custom-work/support durations are excluded.

Diligence Risks

Five Contract and Control Risks to Review

The source labelled these automatic walk-away answers and claimed they reflected prior customers. That experience claim, frequency ranking and universal recommendation are not supported. Evaluate the actual dependency and acceptable remedy before choosing a provider.

Build-only handover

What maintenance, portability and extension rights remain if source is not delivered? Decide what source, documentation or escrow your operation needs and record it in the contract.

Shared administrative access

Require attributable staff actions and suitable permission boundaries. Inspect actual access and audit behavior; a shared interface does not itself prove shared credentials or absent records.

Front-end-only limits

Test protected routes and APIs directly under each role/tier. UI-only visibility is not sufficient evidence of authorization; require the proposed middleware and server-side controls to be demonstrated.

Hosting without a clear choice or exit

Compare customer and provider hosting options, credentials, backups, data export, dependencies and exit assistance. Provider hosting is not inherently unacceptable; evaluate the actual terms and transition work.

Quote without exclusions

Ask for baseline, gaps, customer inputs, providers, custom modules, acceptance, support and full charges. An omission needs clarification, not an assumption about the bidder's intent.

Six Capability Groups to Demonstrate

Six Capability Groups to Demonstrate

These are source specifications to confirm, not proof that every feature currently ships or can be shown in a live demo. Request data-backed acceptance tests for the agreed scope.

Entitlement boundary

Five tier states and route middleware are specified. Test direct links, APIs, privacy and downgrade/upgrade behavior. Clear limits should describe real entitlements without promising that visibility drives conversion.

Profile data and attribution

Experience, education, skills, certifications, projects, publications, patents, volunteering and languages are recorded as separate models. Endorsements and recommendations attach to the giving identity; test attribution, permissions and profile edits.

Hiring state

Seven application states from draft through hired, interviews linked to applications and assessment-attempt records are specified. Test allowed transitions and exceptions; no claim that every hiring task stays inside the platform is made.

Outreach credits

A metered wallet, send logs and operator-set per-tier allowances are recorded. Test grants, debits, failed sends, refunds and abuse controls. Paid outreach does not replace recipient protections or guarantee revenue.

CRM failure visibility

Salesforce and HubSpot push topics with sync/delivery logs are recorded. Test success, failure, retries and operator visibility; confirm connector/account permissions and separately scope other services.

Governance records

Reports, moderation actions, appeals and IP bans are recorded as four distinct types with lifecycles. Test attribution, access, changes and review evidence; records alone do not establish legal compliance or audit acceptance.

Scope Boundaries

Six Limits and Dependencies to Resolve

Raise blockers in the first written brief. A requirement may need a custom module, a revised offer or a different product. No fixed shape, effort ranking or delivery promise is established for additions.

Deployment and customer evidence

This restoration verifies no named customer deployment or customer result. Original tenure, project totals and portfolio assertions are excluded rather than used as credibility evidence. The scenario below remains explicitly authored.

Certification verification

The recorded base scope stores member-entered certifications without checking an issuing body. Manual review, authority APIs and verification evidence are separate proposed work, subject to validation and quote.

Native iOS

Web + Android are recorded scope. PWA installability/offline routes require device and browser tests and do not establish native iOS equivalence. Native iOS account, signing, submission and review work is separate and subject to validation.

Moderation beyond base

Reports, actions, appeals and IP bans are specified. Two-moderator permanent-ban approval and escalation tiers are outside recorded base scope. Determine the controls and staffing your workload needs rather than assuming a volume threshold.

CRM coverage

Salesforce and HubSpot are the two recorded integration topics, subject to confirmed connector/account coverage. Other CRMs, applicant-tracking systems and HRIS services need separate authentication, mapping and failure-handling scope.

Customer accounts and dependencies

Customer control of payment, email, push and OAuth accounts is proposed. Confirm setup responsibilities, permission grants, portability, provider eligibility and ongoing charges. It does not guarantee that leaving requires no migration.

Illustrative Sector Network, Not a Client Engagement

Illustrative Sector Network, Not a Client Engagement

Authored planning scenario only: a sector body considers a shared professional profile, hiring workflow and learning record. Assume, for this example, that credentials, candidate records and training are held in separate systems. This is not a report of any organization, a deployed product, a legal requirement or a customer result.

Scenario propertyRecorded specification or limit
Professional networking, hiring and learningProposed linked workflows to validate with the sector body and actual users.
Tier configurationFive recorded tier states; exact plan boundaries require written scope and tests.
Hiring workflowSeven recorded application states, draft through hired; validate permissions and transitions.
Release and verificationNo deployment window is promised. Issuing-body verification is separate proposed work, not a base capability.

Credentials and authority

The hypothetical body wants verified qualifications. Establish who may verify them, the manual/API route, evidence, revocation and appeal rules with qualified advice. Do not presume that being a sector body supplies issuing authority.

Candidate records and profiles

Test linking the profile to applications and the seven-state hiring workflow. Define migration, updates, permissions and duplicate handling; shared records do not automatically prevent drift.

Learning and profile signals

Courses and profile-linked certificates are recorded. Validate issuance, recognized meaning, recruiter filtering and access rather than assuming completed training is automatically a useful hiring signal.

Proposed combined test: maintain skills, endorsements and appropriately verified credentials on a controlled profile; carry an application through hiring steps; attach a course completion; and review a moderation action and appeal. None of these examples is an observed customer outcome or current readiness claim.

Frequently Asked Questions

Frequently Asked Questions

What professional-network experience is verified here?

No company tenure, project count, named deployment, portfolio claim or customer result is verified by this restoration. Those unsupported credibility claims are excluded. Evaluate the agreed specification, workflow demonstrations, test evidence and signed terms; the sector scenario is authored, not client work.

What would I receive at handover?

The recorded proposal names the Next.js application, Prisma schema and reversible migrations, customer infrastructure/database and customer-controlled provider accounts. Confirm source completeness, dependencies, encrypted-code/callback restrictions, documentation, tests, licence, ownership, resale and exit rights in signed software/third-party terms.

Can credential verification be added?

Treat it as separately proposed work subject to validation. Identify the issuing authority, manual/API process, evidence, permissions, revocation and appeal requirements. Ask qualified counsel or sector bodies about applicable rules; no relative-effort ranking or fixed delivery duration is verified.

What if a requirement is outside scope?

Request an explicit written gap assessment before commitment. Where a module is feasible, agree deliverables, dependencies, tests, total and change approval first. A different product may be appropriate; no blanket ability to build every requirement is claimed.

Who works the moderation queue?

Plan operator staffing, roles, review standards, escalation and coverage. Reports, actions, appeals and IP bans are specified tooling, not a managed moderation service. Confirm staff responsibilities and test scoped accounts; no member-count staffing threshold is assumed.

What support follows handover?

Confirm guidance, defect fixes, updates, monitoring, escalation, exclusions and charges in writing. Original multi-window support durations are excluded rather than offered as a current entitlement. Source handover and independent operation remain subject to signed software/provider terms.

Ask the Scope and Evidence Questions First

Ask the Scope and Evidence Questions First

Send your role/tier matrix, profile and hiring needs, outreach rules, CRM accounts, verification requirements, moderation standards and target devices. Ask for written answers, demonstrations, exclusions, acceptance tests and signed handover/support terms. Email is answered in writing, with no calls required and no phone numbers collected.