Need Senior Laravel SaaS Developer to review and complete billing/payment architecture in existing multi-tenant CRM.

We are looking for an experienced Laravel developer to review, improve, and complete the payment and billing module of an existing multi-tenant SaaS CRM built specifically for moving companies.

This is NOT a new application. The platform is already live and includes:

- Lead Management
- Estimates & Quotes
- Customer Portal
- Moving Agreements / Contracts
- Job Scheduling
- Dispatch & Field Portal
- User Roles & Permissions
- Dashboard Reporting
- Multi-Tenant Architecture

We are seeking a developer who can review the existing implementation, understand the current workflow, and build a complete payment lifecycle that aligns with real-world moving company operations.

---

Important

This project involves working within an existing Laravel application.

Before providing a final quote, we expect the selected developer to review:

- Existing codebase
- Database structure
- Current payment implementation
- Estimate-to-job workflow
- Existing user roles and permissions

We are not looking for someone who will immediately quote the project without understanding the current architecture.

---

Payment Processor Requirements

The platform is multi-tenant.

Each moving company (tenant) must be able to connect and use their preferred payment processor.

Supported processors:

- Stripe
- Square
- PayPal

Requirements:

- Tenant chooses preferred processor
- Tenant connects their own account credentials
- Payments go directly to the tenant's account
- Architecture should allow future payment providers to be added later

Experience integrating Stripe, Square, and PayPal within Laravel is required.

---

Deposit Workflow

Before sending an estimate, authorized users should be able to configure:

- No deposit required
- Percentage-based deposit
- Fixed dollar amount deposit

Examples:

- 20%
- 25%
- 30%
- $100
- $250

Only the following roles should have access:

- Admin
- Manager
- Sales

The selected deposit becomes part of the estimate and follows the customer throughout the booking process.

---

Contract Acceptance & Deposit Collection

After the customer accepts the estimate and signs the contract:

- Deposit invoice should be automatically generated
- Customer should be redirected to the payment page
- Customer should be able to return later and complete payment
- Processing fees should be supported
- Payment status should update automatically

---

Manual Payment Recording

The system must support recording payments received outside of the payment gateway.

Examples:

- Cash
- Check
- ACH
- Zelle
- Cash App
- Other

The system should record:

- Amount
- Date
- Payment method
- Internal notes
- User who recorded the payment

---

Invoice Management

Requirements include:

- Deposit invoice tracking
- Deposit invoice cancellation
- Paid / Pending / Cancelled statuses
- Audit history for payment actions

---

Final Invoice Automation

The system should automatically generate a final invoice when the job is marked completed.

Hourly Jobs

Final Invoice =

(Hourly Rate × Actual Time)

+ Travel Charges
+ Additional Services

- Deposit Paid

Flat Rate Jobs

Final Invoice =

Flat Rate Price

+ Additional Services

- Deposit Paid

The final invoice should accurately reflect the customer's remaining balance after deposit credits have been applied.

---

Final Payment Collection

The customer should be able to:

- Pay the remaining balance online
- Receive payment confirmation
- Receive a receipt
- View payment status

Authorized users should also be able to manually mark invoices as paid when payment is collected outside the system.

---

Paid-In-Full Workflow

Once payment is received:

- Invoice marked Paid
- Job marked Paid In Full
- Customer balance updated to $0.00
- Dashboard updated automatically

---

Revenue & Financial Reporting

Dashboard reporting should include:

- Deposits Collected
- Final Payments Collected
- Outstanding Balances
- Pending Deposits
- Monthly Revenue

Each tenant must only have access to their own financial data.

---

Crew Tip Collection

After job completion, customers should have the option to leave a tip for the crew.

Suggested tip amounts:

- $25
- $50
- $75
- $100
- Custom Amount

Important:

Tips must be tracked separately and should NOT be included in company revenue calculations or financial reporting.

---

Ideal Candidate

We are looking for someone who has experience with:

- Laravel SaaS Applications
- Multi-Tenant Architecture
- Stripe Integrations
- Square Integrations
- PayPal Integrations
- CRM Systems
- Invoicing & Billing Systems
- Payment Workflows
- AWS Deployments

Experience building software for service-based businesses is a strong plus.

---

To Apply

Please provide:

1. Relevant Laravel SaaS projects you have worked on.
2. Experience with Stripe, Square, and PayPal integrations.
3. Experience working within existing codebases.
4. Your estimated timeline after reviewing the project.
5. Any questions you would need answered before providing a final estimate.

We are looking for a long-term relationship. If the developer is a good fit, there will be ongoing opportunities for bug fixes, enhancements, new features, and future development of the platform.