Founding Designer: What I Learned Being the Only Designer 3 Times

A founding designer is the first designer a startup hires, usually before there is a design team, a design process or a design system. You own everything that looks or behaves a certain way: the product, the website, often the brand and the pitch deck. I have been the only designer three times: the first design hire at Accern after its seed round, the sole product designer at Greenely, and the only designer in a company of around 30 people at Bitgrit. The short version of what I learned: the job is less about making screens and more about building the conditions for good design to keep happening after you, a process, a kit and a direct line to users.

This is what that looked like in practice, what I would do again, and what I would tell a designer weighing a founding designer offer today.

What a founding designer actually does

Job posts make it sound glamorous. In reality, a founding designer does three jobs at once.

The maker. You design the flows, the UI, the marketing site and whatever the sales team needs by Friday. Nobody else will.

The builder of the function. You decide how design work gets requested, reviewed and shipped. If you do not set that up, the company will set it up for you, usually as "the PM sends wireframes and the designer colors them in".

The voice of the user. In an early startup, nobody owns the user full time. Founders talk to buyers, engineers talk to tickets. If the designer does not find a route to real users, no one will.

First Round Review's guide to the founding designer role describes it in similar terms: a solo practitioner who also has to represent the whole design function. My experience matches that. The title says designer. The job is closer to a small head of design who still does all the pixels.

Three times as the only designer: what I walked into

Every company was different, but the starting point rhymed.

Accern (2020 to 2022). I joined in January 2020 after the seed round, as the first design hire, while the business moved toward Series A and B. A beta had been built on blue-sky concepts before design existed: prototypes never usability tested, an architecture that did not scale, and two separate products (Titan for text analytics, XYME for predictive analytics) that users had to move between. Our users were large finance enterprises, so few were available to test with. You can read the full story in my Accern no-code AI platform case study and the deeper write-up on enterprise UX when 95% of users never used the product alone.

Greenely (2019 to 2020). A Swedish energy app helping 200,000+ households track and reduce electricity use. I was the sole product designer, and part-time. Before me, PMs created wireframes from blue-sky ideas, nothing was tested, and the app's architecture could not scale. The details are in the Greenely energy app case study.

Bitgrit (2018 to 2019). An AI and data science community of 30,000+ engineers building toward a blockchain-based AI marketplace. I was the only designer among roughly 30 people, responsible for the UX and UI of the product and the website, for users and for clients. See the Bitgrit community platform case study.

Two of the three had the same problem on day one: a product that existed before design did, built from ideas that nobody had tested. That is normal. If you take a founding designer role, expect to inherit decisions, not a blank canvas.

Company	What I inherited	My route to users	What I left behind
Accern	Untested beta, two separate products, heavy jargon	The customer success team, interviews and a usability survey	One product path, a design process, a design system
Greenely	PM wireframes, untested app, weak architecture	A Facebook group of 2,000+ members, and people knocking on the office door	15+ new integrations organized into the app, a design process, a design system
Bitgrit	A platform whose key features users did not understand	7 user interviews and a survey of 20 people	A brand design language, a UI kit that grew into a design system

What the founding designer job is really about: five things that worked every time

1. Start with the whole company in the room

At Accern we ran bi-weekly workshops with different departments to agree on where the product was and where it had to be, plus daily standups with the VP of Product and the PMs. At Bitgrit the first step was brainstorming workshops with marketing, sales and product owners. At Greenely it was workshops on what we wanted to achieve and which pain points users had. When you are the only designer, alignment is your leverage. You cannot out-produce a misaligned company.

2. Find a route to users, even a strange one

This is the part I am proudest of, because it was different every time. At Accern, the users were finance enterprises we could barely reach, so we worked through the customer success team, who knew the clients better than anyone. That is how we learned that 95% of users never used the product by themselves. At Greenely, a Facebook group of more than 2,000 members gave us a research panel, and some users simply knocked on the office door to complain or ask for a feature. At Bitgrit, it was interviews and a short survey. None of those are textbook. All of them beat guessing.

3. Install a process before you scale screens

"Implemented a design process" is on all three case studies for a reason. A lightweight process (research, flows, prototypes, testing, review with developers) is what turns one designer's taste into the company's habit. Without it, every feature becomes a negotiation.

4. Turn the UI kit into a system early

At Bitgrit I started with a UI kit, and it kept growing until it became a design system. At Accern and Greenely, establishing a design system was part of the job too. As the only designer, components are how you multiply yourself: engineers can build a reasonable screen when you are busy elsewhere.

5. Say yes to the non-product work, on purpose

Founding designers end up designing the website, marketing pages and decks. At Accern that included the Series B pitch deck, which I wrote about in designing a Series B pitch deck that raised $40M+. That work taught me how the company was being sold, which made my product decisions better. The trick is to do it deliberately, not as a pile of favors.

What changes for founding designers now

When I was the only designer at those companies, the job ended at the Figma file and a close conversation with developers. Today, many founding designer posts ask for something more: a designer who can also build. My own role went that way at ViewStats, where I worked in the codebase with Cursor, Claude Code, React and TypeScript, shipped components and opened pull requests. The story is in my ViewStats case study.

For a founding designer, that matters more than for anyone else. You are already the bottleneck. If you can take a flow from Figma to a working prototype, or fix the spacing in production yourself, you remove a queue that would otherwise slow the whole company. My AI design experiments are mostly that muscle: Figma as the brief, Claude and the Figma MCP to build, then motion and sound on top. If you want to start, how to become a design engineer is the practical path I would follow.

One limit to this advice: if the startup has a strong engineering team and a product that is mostly forms and tables, coding is a bonus, not a requirement. Judgment about users is still the core of the job.

Should you take a founding designer role?

Take it if you like ambiguity, you want to shape how a company thinks about users, and you are comfortable being judged on outcomes rather than portfolio shots. Skip it, or negotiate hard, if the founders cannot explain why they need design now, or if the role is really "make the PM's wireframes pretty".

Questions I would ask in the interview:

• Who talks to users today, and how often?
• What was built before design, and which of those decisions are open to change?
• Who does design report to, and who settles a disagreement between design and engineering?
• What does success look like for this role in six months?
• Will there be budget to hire a second designer, and when?

On pay and equity, I will not quote numbers here, because they depend on stage, funding, location and how much risk you take on. What I would say is that a founding designer takes early-employee risk and should be offered early-employee terms. If you are new to the role itself, my guide to what a product designer does covers the fundamentals first.

FAQ

What is a founding designer at a startup?

The first designer a startup hires, usually before any design team exists. They own product design end to end and often the website, brand and decks too, while also setting up the design process and system the company will grow on.

What is the difference between a founding designer and a founding product designer?

Mostly the scope of the title. "Founding product designer" signals the product comes first and brand or marketing work is secondary. In practice, at an early startup, both end up touching everything visual.

Does a founding designer need to code?

It is not required everywhere, but it is a growing advantage. Being able to prototype in code or ship small fixes removes you as a bottleneck. Judgment about users still matters more than any tool.

When should a startup hire its first designer?

When the product decisions start to cost real money if they are wrong: around the time you have users you can learn from and a roadmap that is growing faster than the founders can think through each flow. Waiting too long means the designer inherits a product built from untested assumptions, which is exactly what I walked into twice.

How do you survive being the only designer?

Align the company early, find any route to real users, install a light process, turn your components into a system, and protect time for the work only you can do. Everything else is negotiable.

If you are a founder looking for your first designer, or you need someone to set up design at your startup while also shipping it, hire me as your founding product designer. You can see the rest of my client work on my product design work page.