Case study 04 / 05
Production · Friday Ice CreamFridayOps
Internal CRM & Business Operations Platform
- Year
- 2026 — Present
- Company
- Friday Ice Cream
- Type
- Internal Enterprise Software
- Status
- Production / Actively Evolving
- Role
- Sole Software Engineer — Backend & Business Systems
01
Overview
FridayOps is a production internal CRM and business-operations platform used at Friday Ice Cream to digitalize operational workflows, centralize business data, and reduce dependence on fragmented manual processes.
02
Context
Inside a growing company, many business processes don't begin as formal software requirements. They exist as spreadsheets, messages, manual follow-up, department-specific processes, informal approval flows, and repeated administrative work.
FridayOps was created to convert those operational processes into structured software.
03
The Problem
Internal workflows were handled through disconnected processes, which created:
- Limited centralized visibility
- Repetitive manual work
- Difficult follow-up
- Inconsistent data handling
- Information spread across multiple channels
- Difficulty expanding workflows across departments
A generic CRM alone wouldn't solve this — many requirements are operational, not purely customer-management.
04
What I Built
An extensible internal business platform — not a collection of unrelated pages — that progressively absorbs real company workflows.
CRM & Customer Operations
- Customer service
- Complaint management
- Complaint follow-up
- Operational case handling
- Internal workflow tracking
Business Process Automation
Repetitive manual activities replaced with controlled processes and centralized data, instead of tracking tasks in separate files or messages.
Role-Based Access
Users and departments get access based on their responsibilities, so the platform can extend across business functions without exposing every workflow to every user.
Modular Growth — Roadmap
The architecture allows new business areas to be added over time. Expansion areas on the roadmap:
- HR workflows
- Accounting-related workflows
- Commission workflows
- Operational tracking
- Internal administration
05
Engineering Approach
Requirements come directly from employees, managers, accounting, customer-service, and other operational teams. I convert them into domain models, business rules, database structures, APIs, authorization rules, user interfaces, and maintainable workflows.
FridayOps also sits within a broader automation effort at Friday Ice Cream, including master-data and SAP-related workflows.
Understand the business process first, then design the software.
06
Technical Challenge
The hardest challenge isn't a framework problem — it's converting informal real-world processes into software that stays maintainable.
“We currently do this manually, then this person approves it, and then accounting needs this information.” From a requirement like that, I determine:
- What is the actual domain entity?
- Which state should be stored?
- Who owns the process?
- Which roles can change it?
- What should be immutable?
- What should be auditable?
- How should future modules interact with it?
07
Business Impact
FridayOps is actively used within Friday Ice Cream — a real internal production system, not a demo. It helps create:
- More structured workflows
- Better operational visibility
- Less dependence on disconnected manual processes
- More consistent business data
- A reusable foundation for future internal systems
08
My Role
Owned the platform end-to-end, from understanding operational requirements and domain modeling to backend architecture, database design, APIs, authorization, UI implementation, deployment, and ongoing production development.
- Gathering requirements from the business
- Understanding operational processes
- Translating them into software requirements
- System architecture
- Database design
- Backend & API development
- Authentication & authorization
- UI development
- Process automation
- Deployment
- Ongoing feature development
09
Technology Stack
Source code: private repository
Next case study →
Outlet Control
POS, Inventory & Financial Operations System