What Can You Actually Get Done in One Month of Design?

Most founders wildly overestimate or wildly underestimate how much design work fits in a month. The overestimators book a subscription expecting an entire product redesign delivered in 30 days. The underestimators don't start because they assume there isn't enough to fill a month. Both assumptions lead to poor planning.

Here's the honest reality: a productive month of design — roughly 20 working days with a senior designer — is a significant amount of output if you plan it well. The constraint isn't usually capacity. It's the feedback loop. Work moves as fast as you review and respond.

This post breaks down exactly what fits in a month, how long specific deliverables actually take, and how to sequence work to get the most out of your design capacity.

The Baseline: What "One Month of Design" Actually Means

A month has roughly 20 working days. In a subscription model, you're typically working with one designer at a time on one active task. That's not a limitation — it's the structure that keeps work moving cleanly without communication overhead from managing multiple parallel threads.

The effective output of those 20 days depends on three things: the complexity of each task, the speed of your review cycles, and how well your briefs are written. A fast reviewer who writes clear briefs can get through significantly more than someone who takes 3 days to respond to each draft.

With that baseline in mind, here's what actually fits.

A Full Landing Page Redesign: 5–7 Days

A proper landing page redesign — not just visual polish, but a full rethink of structure, messaging hierarchy, and conversion flow — takes 5–7 design days when the brief is solid.

That includes: a wireframe or layout exploration (day 1–2), a high-fidelity design of each section (day 3–5), and one round of revisions incorporating your feedback (day 6–7). If the copy is provided in advance and you have a clear sense of who you're designing for, this timeline holds consistently.

What it doesn't include: writing the copy, technical implementation, or A/B testing setup. Those are separate workstreams. Design hands off a Figma file ready for development.

Where the timeline slips: unclear messaging, copy that changes mid-design, or requests to "try a few different directions" after the initial direction is approved. Direction changes mid-project add 2–3 days per change.

If you're redesigning your landing page, read the startup landing page design breakdown for what makes these projects succeed or fail.

A Dashboard Feature: 4–6 Days

Designing a new feature for an existing SaaS dashboard — say, a reporting view, a settings section, or a new data module — typically runs 4–6 days. This assumes you're working within an existing design system. If there's no design system and we're establishing patterns from scratch, add 2–3 days.

The 4–6 day estimate covers: understanding the feature requirements (which you provide), sketching the interaction model, designing the full screen set, and handling one revision cycle. "Full screen set" usually means the primary view, empty state, loading state, and any modals or expanded states.

What most founders underestimate here is the number of states a single feature actually requires. A reporting view isn't one screen — it's the populated view, the empty state when there's no data, the loading state, the filtered view, the export flow, and any error states. Each state needs to be designed intentionally. Skipping states leads to the half-finished product feel that frustrates users.

An Onboarding Flow: 3–5 Days

Designing a complete onboarding flow — from signup through first meaningful action — takes 3–5 days for a straightforward product. A "straightforward" product has a clear value prop, a definable activation moment, and an onboarding path that doesn't branch heavily.

The 3–5 days covers: mapping the onboarding steps, designing each screen, and working through the connecting microcopy and progress indicators. It does not cover user research to determine what the activation moment should be. You need to bring that clarity to the brief.

If your product requires significant personalization in onboarding — different paths for different user types, complex data imports, team setup flows — add 2–4 days depending on the number of branches.

Onboarding is worth prioritizing early in a month if you're preparing for a launch or if churn is a current problem. The activation rate impact of a well-designed onboarding flow typically outweighs the value of almost anything else you could design that month.

A Pitch Deck: 3–4 Days

A designed pitch deck — not a template fill-in, but a custom designed presentation with your brand, your content, your narrative — takes 3–4 days. This assumes you provide the content (the story, the data, the key messages) and we handle the visual design, layout, and information hierarchy.

Day 1 is structure and template design. Days 2–3 are layout of all slides. Day 4 is revisions.

The single biggest variable: whether the content is locked before design starts. If slide 6 changes completely after day 3, you've reset the timeline for that section. Get your narrative and data finalized before briefing the design work.

Founders often underestimate how much a well-designed deck affects investor perception. The design signals operational quality and attention to detail. A messy deck — even with great content — creates doubt about the team's ability to execute.

A Mobile Screen Set: 4–5 Days

Designing a mobile screen set — 10–15 key screens for a mobile app or mobile web experience — takes 4–5 days. This assumes the product flow is defined (you know what screens need to exist and why) and you're designing within or alongside an established visual direction.

The estimate covers: the primary screens in full fidelity, key interactive states, and a notation pass so developers understand behavior. It does not cover the full spec document for every possible state, which would take significantly longer.

If you're designing a mobile companion to an existing web product, this is often efficient work because the design language is already established. If you're starting from scratch, plan for an additional 1–2 days to establish the mobile visual direction.

How to Sequence a Full Month of Work

Here's an example of a well-sequenced month for a B2B SaaS startup preparing for a Series A:

Week 1 (Days 1–5): Landing page redesign — structure and high-fidelity design. This is a high-visibility deliverable and sets the visual tone for everything else. Do it first while the brief is fresh.

Week 2 (Days 6–10): Landing page revisions (days 6–7), then pivot to a new dashboard feature (days 8–10 for initial designs).

Week 3 (Days 11–15): Dashboard feature revisions and completion (days 11–12), then onboarding flow design (days 13–15).

Week 4 (Days 16–20): Onboarding revisions (days 16–17), then pitch deck design (days 18–20).

Output at the end of the month: a fully redesigned landing page, one new dashboard feature with all states, a complete onboarding flow, and a designed pitch deck. That's a meaningful amount of work, and it's achievable if you review quickly and briefs are clear.

What Most Founders Underestimate

The cost of slow feedback. If you take 3 days to review a draft, you've spent 3 days of the working month on waiting. In a tight month, two or three slow review cycles can cut your effective output in half. The fastest teams treat design review like a daily standup — it gets done same day or next morning.

The breadth of states within a single feature. "Design the analytics page" sounds like one screen. In practice it's 6–8 screens when you account for all the states. Founders who don't account for this end up running out of month before they run out of work.

Ramp time for new context. The first time a designer works on your product, they need context: your users, your brand, your competitive position, your design system (if one exists). The better your initial brief and onboarding materials, the shorter this ramp. Good teams prepare a one-page product brief before starting. This saves roughly a day of back-and-forth in the first week.

The value of completion over coverage. It's better to finish 3 deliverables completely — including all states, with quality — than to get halfway through 6 deliverables. Half-finished design work doesn't ship, doesn't learn, and doesn't create value. Prioritize ruthlessly.

Planning Your Month: A Simple Framework

Before the month starts, answer these questions:

1. What are the 2–3 highest-value design outputs for this month? (Be honest about priority. If the landing page redesign is more important than the new feature, say so.)

2. Which outputs have dependencies? (Don't start designing a feature if the product requirements aren't finalized. Don't design a landing page if the messaging is still being workshopped.)

3. Who is the reviewer on your team, and what's their realistic review turnaround time? (Build the timeline around that, not around ideal conditions.)

4. Is there existing design system to work within, or are we establishing new patterns? (This materially affects how long each task takes.)

With answers to those four questions, you can write a realistic month plan that doesn't set false expectations in either direction.

See our pricing for how the subscription is structured, or check out how the subscription service works if you want to understand the request and review process before starting.

The goal isn't to cram in as much as possible. It's to complete the right things, at quality, in the time available. That's what compound design progress looks like.

---

Frequently Asked Questions