Guildwell

About this template

Guildwell is drawn for a marketplace that stays small on purpose. The demo content is a screened roster of forty designers, engineers and data specialists, and every page carries the same argument: a person read the brief, picked who to approach, and left the numbers where you can check them.

Both sides get a full path. Clients get a hire page, a vetting page that says what each stage tests, a pricing page that shows where the fee sits, and a roles board where every budget has already been agreed. Specialists get a join page, a screening breakdown, and a profile template with engagements, references and a rate that only a client they have proposed to can see. Specialisms and case studies each have a hub and a detail template.

Behind the sign-in there is a working product, not a placeholder: a client dashboard, a post-a-role form, a proposals inbox with filters and pagination, a two-pane messaging screen with four bubble states and a composer, a contract screen where milestones are approved and released one at a time, and a specialist dashboard with invitations and earnings. Sign in and sign up are separate split-screen pages, and the mobile versions use a drawer nav rather than a tab bar.

The category is a starting point, not a limit. Any business that screens supply before it meets demand, and holds money between the two, fits these pages without redrawing them: recruitment and executive search, creative and production rosters, legal and medical locum networks, tutoring and coaching platforms, trades and home-services directories, equipment and studio rental. Specialists become practitioners, providers or crews; roles become jobs, briefs or bookings; milestones become stages or call-offs.

The design system covers colour and spacing tokens with Desktop and Mobile modes, a Geist and Geist Mono type scale where the mono face is reserved for rates, dates and figures, and 27 components with their states. Twenty-nine pages are drawn at desktop and mobile, including the terms, privacy, help centre, 404 and both auth screens. Layer names follow Client First conventions, so the names become your classes.