PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
LinkedIn Clone ยท Features ยท Professional Networks

LinkedIn Clone Features: Profiles, Entitlements and Hiring Workflows

Review a proposed professional network around shared member identity, tier permissions, hiring state, metered outreach and attributable moderation. The recorded design places entitlement checks in middleware rather than relying on hidden buttons; require route-level tests for the scope you sign.

Web + Android - recorded scopeNative iOS scoped separatelyMember-entered credentials are unverified
5Recorded entitlement tiers
7Recorded application states
6Role descriptions below
2Feature comparison tables

Original prices, deployment/custom-work durations, commercial outcomes, live-demo availability and categorical claims about alternative builds are excluded. Source handover, control and independent changes depend on signed software and third-party terms. Features are recorded proposed scope, not evidence of completed acceptance testing.

What the Paid-Tier Boundary Is Intended to Control

What the Paid-Tier Boundary Is Intended to Control

Search and discovery

Expanded search beyond a member's network, persistent saved searches and role-aware access are recorded. Define the free limit and paid entitlements and test denied requests directly.

Profile views and analytics

Profile-view visibility with history and member analytics are recorded paid-tier capabilities. Confirm data visibility, retention and privacy settings without assuming members will pay for them.

Metered outreach

InMail-style credits in a wallet and an attributable send log are recorded. Confirm allowances, balance updates, retry/failure handling and out-of-network permission checks.

Middleware enforcement

Free, Premium, Business, Sales Navigator and Recruiter Lite are the five tier labels recorded in the source. They describe the proposed tier configuration, not affiliation or entitlement to a third-party service. Test each protected route and configurable boundary.

The source says "five people" while listing six roles; all six are retained below. It also claims six surfaces on one API without enumerating a consistent six-surface inventory. The shared REST API is retained as proposed architecture, not a verified surface count.

Role Scope

Feature Set by Role

The six roles share a proposed identity and database model. Source wording says every module can be toggled without code changes; confirm the actual feature-flag inventory, dependencies and access behavior before relying on that breadth.

01 ยท Member

Experience, education, skills, certifications, projects, publications, patents, volunteering and languages have profile sections with a completeness indicator. Connections have pending/accepted states; follows are directional. Recommendations, endorsements, views and mentions are recorded. Completeness and peer statements do not establish verified credentials.

02 ยท Premium member

The same account can receive expanded search, view history, saved searches, outreach credits and analytics through configured entitlements. Define visible free limits and test that changing tiers changes server-side access, not only navigation.

03 ยท Recruiter

Job status, seven recorded application states, saved candidates, recruiter preferences, interviews attached to applications and assessment-attempt records are specified. The pipeline uses the shared candidate profile; test edits and permissions across hiring and member views.

04 ยท Sales team

Lead records with activity history, segmented/tagged lists, saved sales searches, notes, shared leads and teams are specified. Salesforce and HubSpot integration with sync/failure logs is recorded; confirm actual connectors, eligible accounts, permissions and error handling.

05 ยท Company administrator

Company profiles, administrators, followers, company posts with reactions/comments, culture/testimonial modules, employee highlights and company reviews are specified. These are proposed product modules, not client testimonials or evidence of an audience willing to pay.

06 ยท Operator

Member directory interventions include warn, suspend, ban and unban. Reports carry reason/status; moderation actions have moderator attribution; appeals have their own reviewable records. IP bans carry reason/expiry, and feature flags support staged rollout. Test which actions are logged and who can see or change each record.

Compare the Proposed Build With a From-Scratch Bid

Compare the Proposed Build With a From-Scratch Bid

The original heading mentions LinkedIn, Omnistu and from-scratch development, but the table contains only Omnistu and from-scratch columns. That two-route structure is preserved. LinkedIn is a category reference, not an offered product or an affiliation. No competitor service facts or alternative-builder shortcomings are asserted.

CriterionFrom-scratch bidder - what to askOmnistu - proposed scope to confirm
Working readinessWhat exists now, what remains, and which dependencies and acceptance tests determine release?Request demonstrated readiness, a gap list, dependencies, acceptance tests and written release conditions.
Entitlement modelHow will tier states and route-level checks be implemented and tested?Five user-tier states checked in middleware are recorded; confirm every included route and tier boundary.
Hiring pipelineWhich application states, interview links and assessment records are included?Seven application states, application-linked interviews and assessment attempts are specified; require lifecycle tests.
Outreach meteringHow will balances, sends, retries and allowance changes work?Credit wallet with send logs and tier allowances is specified; test accounting and failed sends.
Sales prospectingWhich lead, list, team and connector workflows are scoped?Leads, lists, teams and CRM sync/failure logs are recorded; confirm actual integration coverage.
Moderation and appealsHow will report, action and appeal records relate and be attributed?Separate report, action and appeal records are specified; confirm history, permissions and review states.
Source handoverWhat code, schema, migrations, documentation, rights and restrictions transfer?Next.js/Prisma source and migrations are specified, subject to signed software and third-party terms; confirm completeness and restrictions.
Tier pricingWhich prices, markets, allowances and entitlements are configurable?Operator-set pricing/entitlements by market are recorded; confirm configuration coverage and change tests.
End to End

How the Recorded Workflow Fits Together

01 ยท Build the profile section by section

Dedicated models for experience, education, skills, certifications, projects, publications, patents, volunteering and languages are recorded, alongside completeness. Test editing, visibility and search; profile depth alone does not establish credibility or recruiter demand.

02 ยท Grow connections and follows

Mutual connections carry pending/accepted states. Directional follows apply to people and companies. Suggested people and alumni exploration use the proposed graph; define how graph state affects messaging and feed access.

03 ยท Publish and organize the feed

Media posts, mentions, hashtags, threaded replies, reactions, polls with vote records, saved posts and followable curated collections are recorded. Test moderation and visibility; these mechanics do not guarantee engagement or current profiles.

04 ยท Enforce tier boundaries

The five recorded tiers are user entitlement states checked by middleware. Ask which feature/allowance changes are configuration, which need code and how direct route access is tested after an upgrade or downgrade.

05 ยท Meter out-of-network outreach

A wallet and send log track outreach credits; per-tier allowance is an operator setting. Verify concurrent sends, balance deductions, retries and failure reversals. Metering is not proof of demand or an additional revenue outcome.

06 ยท Keep hiring state attached to the application

Job status, application state, interviews, assessments with attempts, saved candidates and recruiter preferences are recorded. The source alternates between seven states and seven transitions without listing the full lifecycle; require the exact state/transition map and tests rather than assuming those counts mean the same thing.

07 ยท Close the governance loop

Reports have reason/status; actions name the moderator; appeals have independent status. IP bans have reason/expiry and feature flags support cohort rollout. Test review, access, history and rollback; an IP ban alone does not prove persistent-abuse prevention.

Nine Modules and the Questions They Address

Nine Modules and the Questions They Address

The source presents these as indispensable. Their operational topics are retained, but no module is claimed to guarantee hiring value, defensible decisions, revenue or freedom from complaints.

Recorded modulePurpose and acceptance questions
Profile depthCertifications, publications and patents provide structured member-entered information. Which fields are searchable and visible? No issuing-body verification is included.
Recommendations and endorsementsStatements attach to the identity that supplied them. How are attribution, removal and abuse handled? They do not independently verify a member's claims.
Outreach credit walletBalances and send logs support metered outreach. Which events debit or restore credits, and how are allowance changes and concurrent sends reconciled?
Seven application statesA persistent hiring lifecycle is recorded. What are the exact states and valid transitions, and how are corrections and historical changes retained?
Assessments with attemptsAttempt records provide context for a score. What test/version, timestamp, retry and review evidence is retained? A record alone does not settle a dispute.
CRM sync logsDelivery/failure records make connector status inspectable. What retries, alerts, duplicate protection and permissions are included?
Appeal recordsIndependent review status supports a moderation appeal path. Who can submit, review, reverse and inspect a decision? No outcome or complaint reduction is guaranteed.
Feature flagsPer-deployment/cohort controls support staged rollout. Which modules are covered, how are dependencies checked and how is a change rolled back?
Learning credentialsCompleted learning can be written to profiles. Which learning integrations, completion evidence and search/filter behavior are scoped? External course completion or credential verification is not assumed.

Analytics, trending topics, hashtag metrics and influencer models are also recorded. Request their definitions, data sources, permissions and flag coverage; a configurable metric does not prove predictive quality or commercial value.

Technology

The Recorded Stack and Handover Questions

The source specifies Next.js/Prisma rather than PHP, with TypeScript development skills relevant to maintenance. Its months-versus-years development comparison and claim that the entitlement layer determines value are excluded. Confirm readiness and maintainability from evidence.

Backend

Next.js, Prisma, PostgreSQL and TypeScript with reversible migrations are the recorded stack. Confirm actual versions, migrations and rollback tests; no maturity claim follows from the stack name.

API

Domain-grouped REST routes, session-first authentication with bearer fallback, outbound webhook subscriptions with delivery tracking and cron routes for scheduled work are recorded. Review authorization, retries and secrets handling.

Responsive web

Member, company, recruiter and sales views with role-aware navigation and protected routes are recorded. Test desktop/mobile layouts and direct access with each role.

Progressive web app

An installable PWA, service worker, offline routes and a deferred-action queue are recorded. Validate browser/device support, synchronization and sensitive-data behavior; do not treat it as equivalent to native iOS coverage.

Android

A branded Android build using the shared REST API for profile, feed, network, messaging, notifications and jobs is recorded scope. Signing, developer-account responsibilities and store approval need confirmation. Native iOS is separate proposed work, subject to validation.

Entitlements

Five user-tier states checked in middleware are recorded. Test prices, unlocks, allowances and feature flags against the signed configuration inventory rather than assuming all changes avoid a release.

What Needs Separate Scope or Customer Inputs

What Needs Separate Scope or Customer Inputs

Credential verification is not base scope

Members can add certifications, projects, publications and patents, but the source does not include issuing-body verification. A verification workflow and badge scheme need separate written scope.

Native iOS is separate work

Web + Android are recorded scope. The PWA does not establish full iPhone capability or native parity. Native iOS, signing, developer account and review dependencies require separate validation and quote.

Customer-owned provider accounts

Payment-provider, CRM/ATS, contact-import OAuth, email and push accounts/credentials are customer responsibilities in the source. Confirm exact integration scope, eligibility and secure access arrangements; do not send secrets by email.

Four-eyes moderation and escalation

Reports, actions, appeals and IP bans are recorded base controls. Two-moderator confirmation or additional escalation tiers are separate proposed modules, not implied by approval language.

Pricing and member data are operator inputs

The five tiers are recorded, but actual prices, unlocks, allowances and member data must be configured and governed for your operation. Agree migration, consent, rights, retention and deletion; no inherited audience or revenue is promised.

Custom modules and deeper changes need a written gap list, dependencies, acceptance criteria and quote. The source custom-work duration range is excluded. The company page compares delivery routes; its modelled reference scenario must not be treated as a client case study.

Provider diligence
Frequently Asked Questions

Frequently Asked Questions

Can I change what each tier unlocks?

The recorded design uses user-tier states, middleware checks and feature flags for entitlement and allowance settings. Confirm the configuration inventory, change permissions and tests; do not assume every change avoids a code release.

Are profile certifications verified?

No issuing-body verification is included in the recorded base scope. Member-entered credentials, recommendations and endorsements are not independently verified. Scope a verification workflow and badge scheme separately if needed.

How is out-of-network outreach controlled?

The recorded flow checks a credit wallet and logs sends against operator-set tier allowances. Test authorization, balance consistency, failed sends, retries and allowance changes; this is not a revenue guarantee.

Does hiring use the member profile?

The proposed pipeline shares the candidate profile and retains job/application states, application-linked interviews, assessment attempts, saved candidates and recruiter preferences. Require the exact state/transition map and role tests; seven states and seven transitions are not interchangeable.

What happens when a CRM push fails?

CRM sync/failure logs are recorded for Salesforce and HubSpot connectors. Confirm accounts, API coverage, visibility, retries, alerts and duplicate protection with a failure demonstration; logs alone do not guarantee delivery.

Is native iOS included?

No. Web + Android are recorded scope, subject to agreed acceptance tests and store/account responsibilities. The PWA has recorded offline/queue features but iPhone compatibility requires testing. A native iOS build, developer account, signing and review cycle are separate proposed work subject to validation.

Ask for the Tier Boundary and Workflow Tests in Writing

Ask for the Tier Boundary and Workflow Tests in Writing

Send the target audience, role/tier matrix, outreach allowance rules, hiring lifecycle, CRM needs, moderation policy and target devices. Request permissioned test evidence comparing free and paid access against the same controlled data. Demo availability is not verified here. Email is answered in writing, with no calls required and no phone numbers collected.