First month of work develops a founder’s raw idea into tested drafts and a chosen visual direction. Research fills the opening days, wireframes reach real users by mid-month, brand foundations form beside both tracks, and the month closes, holding validated screens plus a working identity ready for styling.
Founders entering design agency for startup engagements usually bring a pitch deck and rough feature lists, so week one gets spent converting ambition into a written scope. Nothing gets drawn until the product’s core job is stated in one sentence that everyone accepts, because screens built before that agreement usually get thrown away once real priorities surface during research.
Product research and mapping
Research consumes the first two weeks completely, and interviews carry most of it. Founders answer daily questions about users, revenue logic, and launch pressure, while five or six potential customers describe how the problem gets handled today without the product existing. Competitor reviews sit beside those conversations, showing which interaction patterns users already recognise and which conventions carry expectations into the new product.
Flow mapping then converts every answer into diagrams, exposing gaps between what founders imagine and what users actually attempt. A payment concept, for instance, gets reduced toward one essential path: connect account, send, confirm, while secondary features move onto a later list. Scope narrows sharply through this stretch, and that narrowing counts among the most valuable outputs any opening month produces.
First wireframes reach testing
Wireframes appear during week two and face users before week three closes.
- Rough clickable drafts get built deliberately fast, since early testing redirects thinking while changes still cost minutes rather than sprints.
- Five participants attempt the core flow, hesitation points get recorded against each screen, and revised drafts return within days, carrying corrections drawn straight from watched behaviour.
- A second round confirms whether corrections actually worked, meaning two complete loops usually finish inside month one.
- Real changes land through this rhythm, a signup flow dropping half its fields after three abandonments, a dashboard reordered once viewers misread its numbers.
- Founders sit inside sessions whenever possible, because watching one person struggle settles internal debates faster than any meeting could.
Brand foundations take shape
Brand work runs parallel from week two onward, covering name refinement, logo directions, colour systems, and typography sized for screens first. Directions arrive in small sets, three logo routes rather than thirty, each shown inside realistic contexts like app icons, mobile headers, and empty states, so founders judge real appearance rather than isolated marks floating against white.
Chosen routes immediately face contrast checks, so colour pairs pass accessibility thresholds before spreading anywhere across files. Tone guidance closes the track, one short document keeping interface copy consistent once screens multiply past anyone’s memory. Month one delivers foundations rather than finished libraries, exactly enough visual decision for wireframes to become styled, buildable screens during month two without pausing for identity debates.
Month one ends with mapped flows, twice-tested wireframes, and a working visual direction feeding straight into the next stage. Startups finishing this stretch carry evidence about their product instead of hopes, and every later decision builds upward from that tested ground rather than from assumptions nobody checked.
