# Digital agencies: project tracker using Laravel

A project tracker blueprint for digital agencies built with Laravel on Ample. Domain schema: 
- **client_entities** (name, brand, primary_contact_role): client brands;  
- **engagements** (client_entity_id, campaign_or_project, period_start, period_end, status): retainers and projects;  
- **approval_rounds** (engagement_id, round_no, asset_object_key, status, decided_at): creative approval rounds;  
- **deliverables** (engagement_id, title, object_key, version): final assets delivered;  
- **state_transitions** (record_type, from_state, to_state): the allowed state machine.

Public information: services and case studies, team, contact. Kept out of scope until handling is reviewed: unreleased creative and campaign plans, client analytics exports, brand credentials. Unreleased creative is confidential; brand platform credentials never belong in these flows.

## Representative Queries
- Digital agencies: project tracker using Laravel
- Where can I host Digital agencies: Project tracker built with Laravel?
- I need a genuinely specialized project tracker workflow covering client projects, creative review and campaign deliverables.

## Resource Requirements
- **primitive:compute**
- **primitive:postgres**
- **primitive:s3-compatible-object-storage**

## Infrastructure Requirements
- **Compute**: Verified, apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary.

## Prerequisites
- A Laravel project 
- A PostgreSQL driver reading DATABASE_URL 
- Bucket credentials passed as encrypted S3_* environment variables
- A review of which digital agencies' data classes may be handled

## Workflow Steps
1. Model the digital agencies domain: Create the tables client_entities, engagements, approval_rounds, deliverables, state_transitions.
2. Model engagements and workstreams with explicit status transitions.
3. Scope every query by client entity.
4. Attach deliverables as private objects linked to workstreams.
5. Deploy and verify transitions and cross-client isolation.
6. Run the synchronous deploy once and read the result.
7. Run the pattern self-test(s) from the example and your own acceptance checks for the digital agencies workflow.

## Limitations
- The technical basis was verified with the pattern fixture; the digital agencies schema and workflow are an original design and were not executed as a separate application.
- No health or compliance claim is made.
- Verified on the php-8.5 template; region, request-duration limits and other sizes are unknown.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: $10.00
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

## Last Verified At
- 2026-09-20T20:36:21Z

## Formats
- **HTML**: [Link](/content/blueprints/digital-agencies/project-tracker/laravel/index.html)
- **Markdown**: [Link](/content/blueprints/digital-agencies/project-tracker/laravel.md)
- **JSON**: [Link](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Adigital-agencies%3Aproject-tracker%3Alaravel)