Skip to content

Client Management App Developer for a Multi-Firm 60-Day Pilot

This client management app developer project asks for the smallest working version of a client management web app that one firm can use for a 60-day pilot. The front end already exists, so the work covers the server, database, and login.

  • Open ยท checked 12 Nov 2026
  • ๐Ÿ‡ฆ๐Ÿ‡บ Australia (budget currency)
  • Javascript
BudgetA$250โ€“1,200 AUD
Timeline60-day pilot
Skills asked7
Posted1 week ago

Is the budget fair? A$250โ€“1,200 AUD looks workable for a basic login, one firm, and a simple data model over 60 days. It is tight if the client expects full security testing and features beyond the stated must-haves.

What the client needs

  • Add email and password sign-up and sign-in with strong password hashing.
  • Keep each firm's data private in a multi-tenant setup.
  • Connect the existing front end to a server and database.
  • Add sign-out and keep users signed in across phone and desktop.

Skills the client asked for: JavaScript, Database Development, Web Development, Backend Development, Frontend Development, Security, API Development.

Where to aim your bid

LowA$395
Sweet spotA$630
HighA$915

The sweet spot sits about 40% of the way up the client's range, the same rule AutoBidPilot uses for its own price suggestions. Go higher when the scope is large or unclear; go lower only when you can show close, finished work. Check what you keep after fees with the bid price calculator.

Across the 4 Javascript briefs we have written in AUD, the median budget is A$615. We wrote 35 Javascript briefs in the last 7 days.

What the project involves

A client management product for professional services firms such as law, accounting and financial advisory has a front-end shell: an installable, responsive web app with offline page and service worker, but no server, database or login, so data lives only in the browser. The client needs the smallest working version that one firm can use for a 60-day pilot.

Must-have features

  • Email and password sign-up and sign-in with hashed passwords (Argon2, bcrypt or high-iteration PBKDF2), sign-out and sessions across phone and desktop
  • Multi-tenant firms where one firm can never see another firm data, with an explanation of how this is enforced
  • Admin and Member roles, with Admins inviting Members by email
  • Clients: add, edit, search and delete, with name, company, email, phone, address, notes and tags or status, searchable by name and company
  • Dated notes showing author and time, with history kept by the firm
  • Responsive, installable web app with server sync
  • Basic audit trail of who created, changed or deleted records, viewable by Admins
  • HTTPS only, data in an Australian region where available, no secrets in front-end code and daily backups

Out of scope

Billing and subscriptions, tiers, TOTP and device-fingerprint login, SAML single sign-on, live location sync, push notifications, a public API, offline write queue and native app store apps.

Acceptance tests

  • New firm sign-up makes the user Admin
  • Add a client with all fields and a note that appears in history
  • Search the client by name
  • Sign out and back in on a phone and see the same data
  • Invite a Member who sees the firm clients
  • A second firm cannot see the first firm clients
  • Deleting a client removes it and shows in the audit trail

Deliverables, ownership and budget

Deliver a live HTTPS test URL, full source in a client-owned repository with a README for running, deploying and backing up, admin access to hosting and database accounts in the client name, and a short note on firm data separation and password storage. The client owns all code, the developer signs a confidentiality agreement before seeing the shell files, and no reuse or resale is allowed.

Budget is up to AUD 1,200 fixed, paid by milestone: login, firms and users; clients and notes; sync, audit trail and polish. If the full scope does not fit, quote login, firms, clients and notes first and price invites and the audit trail as a second stage. Applicants should link similar apps, name their stack and say how they would separate firm data.

How to win this project

  1. Explain how you would keep one firm's data separate from others, not only in the interface.
  2. Name the password hashing method (Argon2, bcrypt, or PBKDF2) you would use, as the client asks.
  3. Show a small login-and-data app you have built with a front end, since the shell already exists.

Questions to ask the client

A specific question in your first message shows you read the brief. Pick one or two:

  • Which hosting and database does the client prefer for the pilot?
  • Must the existing front end be kept in its current framework?
  • What data must be exportable or backed up during the 60-day pilot?

Common questions

How much does a client management app developer cost?

The client posted A$250โ€“1,200 AUD. The description sets a smallest-working-version scope for one firm, so confirm the pilot scope before quoting.

What should a client management app developer show?

The listing names JavaScript, back-end and front-end development, database work, and security. Show a login system with firm-level data separation.

Is this project still open?

We checked this project on 10 November 2026. Projects get awarded, so apply soon; we take a brief down when it closes.

This page is our own summary of a project posted online, written to help you decide and to write a better bid. Projects get awarded or closed, so apply soon; we take a brief down when it closes. No job or income is guaranteed.

Before you apply

To apply for this job you need a free AutoBidPilot account. It takes about a minute:

  1. Create your account with your email, Google or GitHub.
  2. Verify your email. We send you a link; opening it brings you straight back to this job.
  3. Finish a short setup (your skills and pricing), then apply.
Create free account I already have an account

100 free credits when you connect your profile.