Fastik: End to End Product Design for a Creative Platform

Fastik is an all in one workspace built for creative professionals: videographers, editors, motion designers, agencies, and freelancers. The platform brings project management, client communication, file sharing, and feedback into a single environment built specifically around how creative work actually gets approved, instead of forcing creative teams into generic project management tools.

I joined as the product designer responsible for the full scope of the product. That meant the marketing website, the onboarding flow, and the entire product dashboard. I worked directly with the founder from early concept through to a market ready platform.

Before Fastik, the creative teams I spoke with during research were running their business across five or six disconnected tools, and every single one of them described the same underlying frustration. Their work was scattered, their clients were anxious, and revisions were chaos.

Three problems kept surfacing as the real cost of this:

Files lived across Drive, Slack, email, and WhatsApp with no single source of truth, so people wasted hours just locating the latest version of a file.

Client feedback arrived as scattered messages with no connection to the actual frame or moment in a video, so revisions turned into long back and forth threads trying to figure out what "that part" actually meant.

Clients had zero visibility into where their project stood, so they defaulted to messaging the team for status updates, which ate into actual production time.

The brief was not to make a nicer looking tool. It was to remove the actual friction points that were costing creative teams time and trust with their clients.

I started with research, not screens. I mapped the full workflow from project kickoff to final delivery across three types of users: solo freelancers, in house creative teams, and agencies managing multiple clients at once. This mapping made it obvious that almost every pain point traced back to two moments: how feedback gets given, and how clients check on progress. So I treated those two moments as the real design problem to solve, and built the rest of the product around supporting them well.

From there the work split into four connected parts.

Marketing website. A landing page built around a problem first structure. Visitors see the pain they already feel described back to them before the product is even introduced, which builds trust faster than leading with features. Early access and waitlist calls to action are placed at the natural points where a visitor has just been convinced, not just bolted onto the bottom of the page.

Product dashboard. This was the core of the work. A full dashboard covering project management, a portal for clients, file sharing, team messaging, and scheduling. The two pieces I am most proud of solve the two biggest problems directly:

A video feedback interface where comments attach to an exact timestamp in the footage, so a client can point at the precise second they mean instead of describing it in a paragraph. This alone removes most of the back and forth that used to happen over revisions.

A client portal where clients can check progress themselves at any time, which removes the need for status update messages and gives the creative team uninterrupted time to actually work.

Visual kanban boards adapted specifically to how creative review cycles move, rather than a generic task board borrowed from software project management.

Design system. A clean, light, component based system shared across the marketing site and the product itself, so the whole experience feels like one product built by one team, not a marketing site and an app that happen to share a logo.

The result is a single coherent experience from the first visit to the website through daily use of the product. The client portal removed a meaningful amount of the back and forth that was previously consuming the team's time, and the product now has a visual identity distinct enough to stand out in a crowded creative SaaS category.

Fastik is a good example of how I approach any product: find the actual cost of the problem first, design the smallest number of features that remove that cost, and only then worry about how polished it looks. If you are building a workflow heavy SaaS product and your users are drowning in disconnected tools, that is exactly the kind of problem I like solving.