Development Agency
Contact Sign in Get a project quote

Service

Freelancer platform development

For founders and operators of freelance marketplaces, talent networks and vetted expert pools who need profiles, briefs, proposals, milestone contracts, held payments and dispute handling designed around their category of work rather than a general-purpose marketplace script.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A talent network for a particular craft, say technical translation or motion design, starts as a curated list and a founder who matches clients to freelancers by email.

  • It grows.
  • Briefs arrive through a web form and are forwarded by hand; freelancers reply with quotes in different formats; the founder negotiates in the middle.
  • When a client and a freelancer agree, the contract is a thread of messages, the deposit is an invoice from the founder's own accounts package, and the freelancer is paid by bank transfer once the client says they are happy, which the client sometimes forgets to do for weeks.

Where it gets harder

The commission is calculated in a spreadsheet, and so are payouts, so month end is two days of reconciliation.

  • When a client rejects a delivery and the freelancer insists it met the brief, there is no record of what was agreed at each stage, only a long thread with attachments.
  • Freelancers who were vetted carefully at the start drift in quality, and there is no structured feedback to notice.
  • Clients cannot browse who is available, and freelancers cannot see how their proposals compare.
  • The founder is the platform, and the platform does not scale past the founder's inbox.

Scope of the service

What the build covers

A custom freelancer platform build normally covers the whole engagement from brief to payout. Freelancer profiles carry skills from a taxonomy built for your category, a portfolio with media, rates, availability and the vetting status your team assigns. Client briefs are structured by work type, so a translation brief asks for language pair, word count and deadline where a design brief asks for formats and usage. Proposals from freelancers answer a brief with a price, milestones and a message, and the client compares them side by side. A milestone contract fixes the agreed scope, price and dates per milestone; the client funds each milestone through the payment adapter and the funds are held until delivery is accepted or a dispute is resolved. Messaging per project keeps every exchange and file against the contract. Delivery and acceptance happen per milestone, with the client accepting, requesting changes within the terms, or raising a dispute. A dispute queue gives your dispute handler the contract, the deliveries and the messages, and records the decision and any split of the held amount. Ratings run both ways after completion. Commission is calculated per contract and payout statements are produced for freelancers on your schedule.

We map your category with you first: how briefs are really described, what a milestone looks like in your kind of work, how vetting is done, what commission model you run, how disputes have actually gone, and which payment provider will hold and release funds. Each becomes a named stage in the scope document.

Deliberately out of scope

  • Acting as the freelancer's employer or agent, tax or employment-status determinations, which the platform does not make, and the accounting of your own business beyond commission and payout statements. Payment holding runs through a payment provider that supports it, under that provider's terms, and the scope document names the provider

When the scope grows

Scoping scenario

A vetted network of clinical translators wants a two-stage vetting process with test pieces, briefs that must be matched only to freelancers holding a particular certification, milestone contracts with a reviewer step between delivery and client acceptance, and payouts twice a month with a commission that falls as a freelancer's completed volume rises. The reviewer step and the tiered commission make this a custom build, and the scope document says so plainly.

Deliverables

What you receive

  • Discovery notes from walking through a real engagement in your category from brief to payout
  • A written scope document naming each stage, the commission model, the dispute process, the payment provider and what is left out
  • Designs of the freelancer profile, the brief and proposal comparison, the contract with milestones and the dispute view
  • The build, including payment holding, disputes and payout statements where in scope, deployed to your hosting or ours
  • Migration of freelancer profiles, clients and open engagements from your current list or tool
  • Training for your operations team and dispute handler, with written guides for freelancers and clients
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access to your current list, forms, payment and accounts tools; your vetting criteria, commission model and the payment provider under consideration.

    Project stage: Onboarding

  2. Planning

    Discovery with the founder and whoever handles disputes and payouts; the brief structure, milestone rules, dispute process and commission are written into the scope document.

    Project stage: Planning

  3. Design

    Profiles, brief and proposal screens designed for clients and freelancers on any device; the dispute and payout views designed for your operations team.

    Project stage: Design

  4. Development

    Built in layers: profiles and vetting, then briefs and proposals, then contracts, payment holding and messaging, then disputes, ratings and payouts.

    Project stage: Development

  5. Client review

    A handful of your freelancers and friendly clients run real engagements end to end with the provider in test mode and tell us where the flow breaks.

    Project stage: Client review

  6. Revisions

    Changes from the review are made and re-checked against the scope document.

    Project stage: Revisions

  7. Ready for launch

    Profiles migrated, payment holding and release verified against live provider accounts you control, payout statement checked, launch checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    Engagements run through the platform; hosting and maintenance continue under their own agreement if taken.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Payment providers that support holding funds and split payouts to freelancers
  • Identity verification providers for freelancer onboarding, as a record of the result
  • Accounting software for commission revenue and payout reconciliation
  • Email and SMS providers for proposal, milestone and dispute notifications
  • Video meeting platforms for briefing calls
  • E-signature providers for platform terms and contract confirmation
  • File storage for large deliveries

How we would approach it

Worked example

Concept demo

A vetted translator network with a reviewer step

The situation

A network of clinical translators wants two-stage vetting with a test piece, briefs matched only to freelancers who hold a particular certification, a reviewer step between delivery and client acceptance on every milestone, payouts twice a month, and a commission rate that falls as a freelancer's completed volume rises.

Why it is a custom build

The custom route is needed because of the reviewer step inside the milestone flow and the tiered commission, which go beyond the direct delivery-to-acceptance flow and flat commission the package assumes.

The scope we would propose

  • A vetting pipeline with test piece upload and reviewer marking
  • A certification attribute on the profile that filters proposal invitations
  • A milestone state for reviewer approval before the client sees the delivery
  • A payout run on two fixed dates with statements per freelancer, and commission tiers calculated from completed contract value over a rolling period

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of work types and the depth of the brief structure for each
  • Vetting process and whether it involves test pieces or reviewers
  • Payment provider and how milestone holding and release will work with it
  • Commission model: flat, tiered or differing by category
  • Dispute process depth and whether partial releases are allowed
  • Payout schedule and the statements required
  • Volume of profiles, clients and open engagements to migrate
  • Hosting choice: your own hosting or ours

Start from a package

Freelancer marketplace package

Freelancer profiles, structured briefs with proposals, milestone contracts with held payments, project messaging, disputes, two-way ratings and payout statements for marketplace operators.

Custom build
View the package

FAQ

Frequently asked questions

When is the package enough and when do we need a custom build?

If a configurable skills taxonomy, structured briefs, milestone contracts with held payments, a dispute queue and flat commission cover your model, the freelancer marketplace package is the right fit and we quote for that. Reviewer steps inside milestones, tiered commission, matching rules based on certifications or a multi-stage vetting pipeline point to the custom route.

How are held payments handled?

Through a payment provider that supports holding funds and paying out to a third party, connected during the build and named in the scope document. The platform records the funding, the hold and the release against each milestone; the funds themselves sit with the provider under its terms, not with the platform or with us.

Does the platform decide employment status or tax for freelancers?

No. It records who contracted with whom, for what and for how much, and produces statements. Questions of status, tax and the terms between you and your freelancers are for your own advisers, and the platform terms you publish are yours.

Can you move our existing freelancers and clients across?

Yes. Profiles, portfolios, client accounts and open engagements are migrated from your current list or tool, and freelancers are invited to complete the fields the new taxonomy needs. The scope document states what can be carried over once we have seen the data.

Who owns the platform afterwards?

You do. The source code, profiles, contracts and records are handed over at delivery. Hosting and maintenance are optional and agreed separately.

Get a project quote for freelancer platform software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences