Service business client portal
An accounting firm needs a custom portal where clients upload documents, see deliverable status, sign engagements, and pay invoices — built with auth and DB.
Tier 4 · Web & Digital · $1000 · 40–50 hrs · 30 day turnaround
Listed price is the project base price. A 3% payment processing fee is added at checkout. The full total is charged upfront when you place your order.
Build a custom web application with user authentication, database, and core business logic using no-code/low-code tools.
A vetted high school student will build a fully functional web application tailored to your business processes, complete with user login, a structured database, and working core features—all delivered as a live, usable product. You'll receive comprehensive documentation so your team can manage users and understand how data flows through the system. This is ideal if you need a working tool faster and more affordably than hiring a full development firm.
A written requirements document describing your core business process (e.g., how customers place orders, how staff track projects, what data fields matter most), any existing spreadsheets or sketches showing your current workflow, and login/permission rules (e.g., admin users vs. regular users).
The student will scope and design your database schema, configure user authentication (login/password, role-based access), build out your specified core features using low-code platforms like Bubble, Airtable, or Retool, test all workflows end-to-end, and document every step for handoff.
A live web application with a working URL, a user-facing guide (screenshots, step-by-step instructions for common tasks), an admin guide (how to add/remove users, reset passwords, access reports), a complete database schema diagram, and API documentation if applicable to your platform choice.
Your $1,000 payment is held in escrow and only released once you've tested the application, verified all user roles function correctly, and confirmed the documentation matches the delivered features.
An accounting firm needs a custom portal where clients upload documents, see deliverable status, sign engagements, and pay invoices — built with auth and DB.
An operations team running on 8 spreadsheets needs a custom internal app with auth, role-based access, and dashboards consolidating the workflow.
A founder building a 2-sided marketplace for a niche service needs an MVP web app with provider profiles, search, booking, and payments.
A nonprofit managing 200+ annual memberships needs a portal where members log in to renew, update contact info, and see renewal status. The student builds a form-driven app with an expiration date tracker, automated email reminders, and an admin dashboard showing past-due renewals and payment history.
A recruiting firm currently tracks candidates in four separate spreadsheets and email folders. The student consolidates this into a single app where recruiters log candidate details, stage (sourced, phone screen, interview, offer), notes, and next action. Candidates log in to check application status.
A school's media lab has 80 cameras, tripods, and lights. Staff need a fast way to check out and return equipment, see who has what, and flag overdue items. The student builds a searchable inventory app with checkout history, due dates, and an admin view of all outstanding loans.
Common platforms are Bubble, Airtable, Retool, and Zapier-linked stacks. You can express a preference in your requirements, but the student and PM will recommend based on your specific feature set and long-term scalability. Platform choice is finalized during the kickoff call.
The student can implement 3–5 distinct roles (e.g., admin, manager, staff, viewer) with different access to features and data. More granular permission schemes may reduce the scope of other features or require a tier upgrade.
Minor tweaks (e.g., a field label change, a small workflow adjustment) can be covered as revisions during the 30-day window. Significant feature additions or design overhauls fall outside scope and may be scoped as a separate project.
No. The student delivers a live, working application and hands over all documentation and access credentials. Hosting, maintenance, backups, and scaling beyond 30 days are your responsibility, though the documentation will include setup guidance.
Basic integrations (e.g., sending emails on a trigger, reading data from Google Sheets) are feasible within scope. Complex integrations with proprietary APIs or payment platforms like Stripe may exceed the tier; those will be flagged in kickoff and scoped separately if needed.
Select a scope and let your Shamrck PM handle the rest. Pay the full total upfront at checkout, then review and approve the completed deliverable. Approval does not trigger a new charge.
Already have an account? Log in