SL Operations
We built SL Operations to keep the records behind our business together. Clients, contracts, work logs, meetings, expenses, and invoices live in one workspace, with each record connected to the client it belongs to.
- Status
- Internal application
- Built with
- TypeScript, Next.js, Bun, PostgreSQL, AWS
The problem
Client work creates more than a deliverable. Agreements, time records, meeting notes, expenses, and invoices all need to stay connected. When those records live in separate files and tools, routine business work becomes a search for the right information.
What we built
- A client workspace that brings contracts, work logs, meetings, expenses, and invoice history together.
- Work timers and logs for recording what was done and how long it took.
- Billing that turns reviewed work logs into editable invoices, with printable and downloadable PDFs.
- A Money area for billing, receivables, expenses, and receipt suggestion review.
Financial records stay under human review. Receipt suggestions are confirmed before becoming expenses, and invoices are reviewed before being marked sent.
How it is built
The application uses Next.js and TypeScript, runs with Bun, and stores its records in PostgreSQL. Microsoft sign-in protects the workspace. Private documents and client logos are served through authenticated routes, and AWS infrastructure is defined in code.
Where it stands
SL Operations is an internal application for Sqware Logics. Its current scope includes clients, contracts, work logs, work timers, meetings, expenses, billing, and receivables.