Landing & Trust
The marketing surface plus the company, trust and legal pages that make a marketplace credible.
A marketplace where verified university students take on paid work: posted as a job with bids, or bought as a gig at a fixed price. Escrow holds the money from hire to payout, and every movement of it is on the record.
University verification is a gate on earning, not a badge
University students with a skill and time, and the clients who would rather hire one than an agency.
Verified students only. University verification is a gate on earning, not a badge added afterwards.
Escrow from hire to payout, with every movement of money on the record for both sides to see.
Change requests, disputes and refunds are first-class paths, resolved in-platform with a stated reason.
A visitor browses, a student earns, a client hires, an admin settles. They share one set of screens rather than four separate products that have to agree with each other.
Browses the directory, the jobs board and the gig marketplace, and reads the bilingual help centre, without an account.
Verifies their university, builds a profile, bids on jobs or sells gigs at a fixed price, and withdraws earnings.
Posts a job and picks a bid, or buys a gig package outright. Funds the wallet, accepts delivery, leaves a review.
Oversees payments, confirms university verification, and resolves disputes fairly and on the record.
Public discovery, identity, profiles, the two hiring paths, delivery, money and administration, plus the support and system states that decide whether a marketplace feels trustworthy.
The marketing surface plus the company, trust and legal pages that make a marketplace credible.
Sign up, sign in, password recovery, and the settings that end with account deletion.
The gate on earning. A student cannot bid or sell until their institution is confirmed.
Blocks and themes, so an expert profile reads as theirs rather than as a filled-in form.
Browse and filter verified students by skill, rating, price and availability.
Client-led work: a brief, a budget range, an optional deadline, and bids against it.
Price, delivery days and a cover message, and a private thread opened with the client.
Student-led work: fixed-price packages with defined scope, revisions and delivery time.
Create, edit and manage packages, with orders tracked from purchase to acceptance.
Where both paths converge: delivery, versions, messaging, disputes and reviews.
Deposits, escrow, platform fee and withdrawals, with a complete transaction history.
The operator console, and dispute resolution that is fair, documented and in-platform.
The money is held safely between hire and payout, and the badge on each step is the entry the wallet history shows for it, so both sides can always see where the money is.
The client tops up their wallet before hiring, so the money is ready when the work is agreed.
Accepting a bid or ordering a gig moves the amount out of the client’s balance and into escrow.
The student submits a note and a link. Every resubmission is kept as its own version rather than replacing the last.
Once the client accepts, escrow releases to the student, minus the platform fee, and the student can withdraw their earnings.
The ledger as a student or client actually reads it: one row per entry, typed, signed, and in the order it happened.
A client who knows exactly what they want buys a gig. A client who wants options posts a job and reads bids. Both end in the same workspace, against the same ledger.
Verified students bid with a price, a delivery time and a cover message. Bidding opens a private thread, so the conversation starts before the hire rather than after it.
The single most important screen in the product, and the one place both hiring paths converge on. It shows each person what they need, and changes as the job moves forward.
Single-page site with a hero, lookbook gallery, countdown and an email capture form. Design is ready; needs to be fast on mobile data and deployed to our domain. Deliver the repo plus a short handover note.
Accepting a bid secures the amount in escrow and starts the job.
The student submits a note and a link; every resubmission is kept as its own version. The poster accepts and completes, requests changes, or escalates, and the record of all three survives.
A title, a description, a category, a budget range and an optional deadline. Verified students bid with a price, delivery days and a cover message, and bidding opens a private thread with the client.
Students publish packages with defined scope, included revisions and a delivery time. A client orders one outright: no negotiation, no bid to evaluate.
However the work was agreed, delivery, messaging, disputes and reviews happen in the same workspace and against the same escrow ledger. There is one way for work to finish.
Change requests send the delivery back with notes. If the two sides still disagree, either can raise a dispute, and it is settled in-platform with the decision explained.
Verification, escrow, versioned delivery, automatic refunds and a dispute path that actually resolves: these are the features that decide whether anyone uses the good ones.
A student cannot bid, sell or be paid until their university is confirmed. The badge is a consequence of the gate, not a decoration.
Every movement of money appears in the wallet history, clearly labelled, so both sides can see what they paid, earned and were charged, and reconcile it.
When an order does not go ahead, the money goes back to the wallet it came from automatically, without anybody having to chase it.
A help centre in both languages, and system states designed rather than defaulted: “no bids yet” says what to do next instead of showing an empty table.
An operator console that oversees payments, verification and disputes, because a marketplace runs on the operator as much as on the software.
Campus Expert can be deployed for a single institution, a consortium, or an open market, with your own verification rules, fee structure and payout process.