The Studio · Custom Business Software
A business platform built around the way The Studio actually works.
The Studio is a custom CRM and project-management application designed around the real workflow of a local interior-design business.



Project overview
Software shaped around the business.
The Studio needed a centralized system for the clients, projects, ongoing work, and internal operations that make up its day-to-day business.
Instead of asking the company to reshape its process around generic project-management software, the application was designed around the way the team already worked.
The challenge
One business workflow, spread across separate tools.
Client and project information lived across disconnected workflows. Generic software could cover parts of the process, but it did not reflect how the company moved from customer relationships into active projects and ongoing work.
The product challenge was to understand that operation clearly enough to create one useful system around it.
The solution
A native application designed from the workflow outward.
Luke designed and developed a native iOS application specifically for The Studio. It brings client information, project management, workflow, and business operations into a product built for the company.
The technology supports the product, but the starting point was the business: learn how the work happens, identify what belongs together, and build software that fits.
Product walkthrough
One platform for the work around each project.
Each part of the product connects back to how the company manages its clients and ongoing work.

01 · The business system
An operational view across the company.
The Studio Feed brings active projects, unread communication, pending documents, and recent activity into one business-wide view. The product is not limited to tracking one project at a time; it helps the team understand what is happening across the operation.

02 · Clients
Clients and projects stay connected.
The client workspace gives the team one place for customer relationships and the project work connected to them, including a clear distinction between active and inactive clients.

03 · Project management
The full project, not just a task list.
The designer view organizes project progress, phases, issues, work in progress, completed steps, and previous updates around the actual interior-design engagement.

04 · Documents and review
Files move through a real review workflow.
Project documents bring files, reference imagery, folders, categories, and approval states into the project itself. The workspace supports review work rather than acting as a passive file list.

05 · Curated inspiration
Design collaboration belongs inside the product.
The inspiration workspace keeps visual direction alongside the client and project it belongs to. It is a clear example of software shaped around an interior-design company instead of a generic project-management template.
Role-aware product design
One project, two purpose-built experiences.
The same Juniper House Renovation is presented differently depending on who is using the platform. The designer needs operational detail; the client needs a clear view of shared progress.
Designer experience
Operational context
The internal view includes project phases, issue and progress states, and previous updates for managing the work.

Client experience
Useful shared progress
The client view simplifies the same project into the status and timeline information that is most useful to the customer.


Client portal
The client experience is a product of its own.
Clients receive a focused dashboard for project dates, estimated completion, overall progress, messages, and recent activity. It is designed around what a client needs to understand, not as a reduced copy of the internal dashboard.
Engineering
Built as a real product, not a prototype.
The application is a maintained business tool. Its technical foundation is intentionally focused on a native experience and a codebase that can continue to evolve with the company.
Native iOS
A native iOS product built for the devices and interaction patterns the team uses.
Product approach
The product structure follows the company’s clients, projects, workflow, and business operations.
Outcome
A product that became part of the operation.
The application became a central part of how The Studio manages its clients, projects, and everyday work rather than remaining a side project or demonstration app.
As its role grew, several workflows previously handled through separate software—including parts of the company’s QuickBooks-based process—moved into the custom platform. The product has continued to expand as the needs of the business changed.