How do I get started?

To get started with the subscription, we need to understand what kind of requests you want to solve, how often they appear, and what brand, website, or product system already exists. From there, we review availability, confirm whether the format fits, and set up onboarding so you can submit requests in an organized way.

A good start is not loading random tasks

Starting well means turning scattered needs into an operational queue. Your team may have design, marketing, Webflow, or UI requests, but if they arrive without priority or context, the first month gets spent organizing. We prefer to do that cleanup at the beginning.

Onboarding defines where requests are loaded, how material is shared, who approves, how review happens in Figma, and which channel is used for daily communication. We use tools like Slack, Asana, Loom, and Figma because they keep a record and reduce unnecessary meetings.

What to bring to the first review

• Request list: even if it is messy, it helps estimate the type of demand.
• Business priorities: campaigns, launches, sales, product, or web maintenance.
• Existing assets: brand, templates, site, access, Figma files, and sales materials.
• Constraints: internal dates, approvers, dependencies, and external resources.
• Flow owner: one person who orders requests and consolidates feedback.

We may also say the subscription is not the right format

If what you need is an identity from scratch, a repositioning, or a full website, the subscription is probably not the first step. In that case, it makes more sense to review a defined scope branding or web design project.

Start when you have recurring demand and someone on your team can prioritize it; without those two conditions, the subscription loses strength.