Short answer: A complete SaaS design project should deliver four things: a feature list that defines the scope, user flows that show how people move through the product, a full interface design built on a design system, and a build plan that tells developers what to build and in what order. If any of the four is missing, the design is incomplete, and the gap usually shows up later as delays or extra cost during development.
What is a SaaS design project?
A SaaS design project is the phase before development where the product is defined and designed in full. It turns an idea, or an existing product that needs to be redesigned, into a set of decisions and screens that developers can build from. It covers what the product does, how people use it and what it looks like.
It is different from a logo or a marketing website. It designs the product itself: the dashboard, the forms, the tables, the settings and every screen a user touches.
What are the four deliverables?
1. Feature list
The feature list defines exactly what the product will do. It names each feature, describes it in plain language and often marks which features are needed at launch and which can come later.
Why it matters: the feature list is the scope. It is what the price and timeline of development are based on. Without it, "build the product" means something different to every person involved.
2. User flows
User flows map the steps a person takes to complete a task, such as signing up, inviting a teammate, creating an invoice or renewing a subscription. They show the order of screens, the decisions along the way and what happens when something goes wrong.
Why it matters: flows are where most usability problems are caught. A feature can look perfect as a single screen and still be confusing as a sequence.
3. Full interface design
This is the visual design of every screen in the product, usually delivered as a Figma file. A professional design is built on a design system: a shared set of colors, typography, components and layout rules, so new screens can be added later without breaking consistency.
Why it matters: this is what developers build. The more complete it is, the fewer guesses they make, and guesses are where products drift.
4. Build plan
The build plan translates the design into development work. It groups features into stages, sets the order in which they should be built and gives a realistic estimate of how long development will take.
Why it matters: it turns a design into a schedule and a budget. It also lets you compare development quotes fairly, because every developer is quoting on the same plan.
Are wireframes included?
Not always, and they don't have to be. Wireframes are low-detail sketches of a screen's layout. Some studios deliver them as a separate step before the visual design. Others go straight from flows to full interface design, especially when the product type is well understood. What matters is that the final interface design is complete. Wireframes are a means, not a deliverable you need to own.
What is usually not included?
A SaaS design project typically does not include:
Development (writing the code), which is a separate phase.
Branding such as a logo, unless it's added as a separate piece.
A marketing website, which is designed separately from the product.
A mobile app design, if the main product is a web app. A mobile version is often a separate add-on, because a good mobile layout is redesigned, not just shrunk.
An admin panel for your internal team, which is a separate surface from the customer-facing product.
Check these explicitly in any quote, because they are common sources of misunderstanding.
How long does a SaaS design project take?
Usually two to four weeks for a focused product, longer for complex ones. The main factors are the number of screens, the number of user roles (for example, customer, staff and admin) and how much of the product is already decided before design starts.
What should I check before paying for a design project?
Ask these questions:
Is there a feature list, and will I approve it before visual design starts?
Will user flows be designed, or only individual screens?
Is the interface built on a design system I'll receive?
Is there a build plan with stages and a development estimate?
How many revision rounds are included, and how does a round work?
Do I own the design files in full once it's paid?
If the answer to the first four is yes, you are buying a complete design. If not, you are buying pictures of screens.
What does a good feature list look like?
A good feature list is short enough to read in a few minutes and specific enough to price. Each line names a feature, says who uses it and describes what it does in one sentence. It is usually grouped by area, such as accounts, billing, reporting and settings, and each feature is marked as needed at launch or later.
Here is a simplified example for a booking product:
Area | Feature | Who uses it | Launch or later |
|---|---|---|---|
Accounts | Sign up and log in with email | Customers, staff | Launch |
Bookings | Book an available time slot | Customers | Launch |
Bookings | Reschedule or cancel a booking | Customers | Launch |
Payments | Pay online when booking | Customers | Launch |
Staff | See today's bookings in one list | Staff | Launch |
Reports | Monthly bookings and revenue | Owner | Later |
Notifications | Reminder message the day before | Customers | Later |
A list like this does more than describe the product. It shows where the effort is, where the risks are and what can safely wait.
What are the most common mistakes in a design project?
Skipping the scope. Jumping straight into screens before agreeing on the feature list. The result looks finished but nobody can say what's included.
Designing only the happy path. Showing what happens when everything goes right, and leaving out errors, empty screens and edge cases. Developers then invent these on their own.
Designing for the demo. Making screens that look impressive in a presentation but are slow to use every day. Products used for hours a day need efficiency more than decoration.
No design system. Delivering screens without shared components and rules. The first new feature after launch then has nothing to follow.
Too many decision-makers. Feedback from several people that contradicts itself, sent at different times. One person should consolidate feedback on the client side.
How is a design project usually run, step by step?
Brief. The client describes the product, users, goals and budget in writing.
Scope. The studio replies with a scope, price and timeline.
Feature list. Drafted and agreed before visual work starts.
Flows. The main tasks are mapped step by step.
Interface design. Screens are designed on a design system.
Revision rounds. Feedback is collected into lists and applied.
Build plan. The work is organized into stages with an estimate.
Handover. Design files, design system and build plan are delivered.
Each step depends on the one before it. When a step is skipped, its questions come back later, usually during development, when they're more expensive to answer.
Key terms
Scope: everything the product will include, defined by the feature list.
User flow: the sequence of screens and decisions for one task.
Design system: the shared colors, typography, components and rules.
Component: a reusable interface piece, such as a button or table.
Build plan: the order and estimate for development work.
Handover: delivering the finished design to the people who will build it.
How Layerice handles this
Layerice is a software design and development studio that designs and builds B2B SaaS products and internal business systems. Its Design service includes a feature list, flows and a build plan, plus the full interface in Figma. It is priced per project: Starter at $6,000 for up to 10 screens (about two weeks) and Full at $8,000 for up to 20 screens (about three weeks). Every design piece includes three revision rounds, and the client owns the design in full once it is paid.
Frequently asked questions
Is a SaaS design project the same as UI/UX design?
It includes UI and UX design, but it is broader. It also defines the scope through the feature list and plans the build, which pure UI/UX work often leaves out.
Can I take the design to any developer?
Yes. A complete design with a build plan is meant to be buildable by any competent development team.
Do I need a design project if I already have a few screens?
Usually yes, but it can be shorter. Existing screens can be expanded into a full design system instead of starting from zero.
What format is the design delivered in?
Most studios deliver in Figma, which developers can inspect directly for measurements, colors and assets.
Why not design and build at the same time?
Because development keeps hitting decisions that haven't been made yet. A short, complete design phase followed by development is usually faster overall.
Does the design include the admin side of the product?
Not always. Customer-facing screens and the internal admin panel are often designed separately. Ask which one a quote covers.
How many screens does a typical SaaS product have?
A focused product often has 10 to 20 core screens. Products with several user roles, dashboards and integrations can have many more.
Can the design change after development starts?
Small adjustments are normal. Large changes during development cost more, because they often mean rebuilding work that's already done.
What happens to the design after launch?
It becomes the reference for every new feature. A design system makes it possible to extend the product without starting over.