00Portfolio and case studies

Every project tellsa business story.

A screenshot without context proves visual skill. A clear case study proves judgment. So every project below leads with the situation, the constraint, and the decision — and the pictures come second.

01Selected work

The decisions behind the deliverables.

Filter by type of work

Showing 8 of 8 projects.

01Website and booking systemLive

The K9 Inn

A boarding and daycare business got a website that takes bookings from a phone, which is where its customers actually are.

Situation: The business needed a website that presented the facility credibly and let an owner move from interest to a booked stay without a phone call.
Constraint: People leave a dog with a stranger only when they trust the place. That trust is built by seeing the actual facility and the actual animals, not by stock photography of generic happy dogs — and all of it had to load and work on a phone, one-handed, before a trip.
Decision: Build mobile-first and lead with real evidence of the facility. Photography of the actual dogs and grounds carries the trust, service and pricing information is reachable without a call, and the booking path is present on the first screen instead of buried behind a contact form.

System createdCustom mobile-first website · Services and pricing presented without requiring a phone call · Booking integration reachable from the primary screen

Read the case study — The K9 Inn

02Wholesale e-commerce websiteLive

Global Brands Express

An importer of German food products got a storefront that works for the wholesale buyers who actually place the orders.

Situation: The business needed a professional storefront that could present a wide product range and support wholesale purchasing rather than only browsing.
Constraint: A wholesale catalogue and a retail catalogue want opposite things. A restaurant buyer arrives knowing the category and the case quantity and wants to get to it in two clicks; a curious shopper wants to be led. Building only for one loses the other, and the buyer with the purchase order is the one who pays.
Decision: Organise the site around product category first, since that is how a buyer already thinks about the order. Categories sit in persistent navigation, the import story establishes provenance without blocking the path to product, and the wholesale route is explicit rather than hidden behind a contact form.

System createdE-commerce storefront with a persistent product category structure · Category navigation matching how buyers order — restaurant line, baking ingredients, preserves, canned goods, seasonings · Wholesale purchasing path

Read the case study — Global Brands Express

03Brand website and community programLive

Heroes of Tara

A mythology-driven brand got a website and a community program built around the story rather than bolted onto it.

Situation: The brand needed a website that carried the world convincingly, and an ongoing community and social program to sustain an audience between releases.
Constraint: An audience that arrives for a world will not tolerate marketing that sounds like marketing. Anything that broke the tone would cost more attention than it earned — but the site still had to sell, and community management still had to run on a schedule rather than on inspiration.
Decision: Let the world do the selling and keep the commercial path inside it. Illustration and mythology carry the site, the purchase and community routes sit in the primary navigation rather than being disguised, and social content was built as a repeatable program in the same voice instead of a series of one-off posts.

System createdBrand website carrying the illustrated world · Clear routes to purchase, community, and background material · Ongoing community management program

Read the case study — Heroes of Tara

04Website for a religious organizationLive

House of Ravenwood

A religious organization got a clear public home for what it believes, who it is for, and how to take part.

Situation: The organization needed a credible public presence explaining its beliefs and practices, and giving people a way to find and join a community.
Constraint: Someone researching a faith community is often doing it privately and cautiously, and is trying to work out whether it is legitimate and whether they would be welcome. That reader is served by directness and structure, not by persuasion.
Decision: Prioritise plain explanation over persuasion. Beliefs, practices, and participation are laid out so a cautious visitor can answer their own questions without contacting anyone first.

System createdPublic website for the organization · Structure covering beliefs, practices, and community · A route to participation for new visitors

Read the case study — House of Ravenwood

05Campaign website and digital operationsLive

Caitlyn for Georgia 9

A congressional campaign website built as an organizing tool rather than a digital brochure.

Situation: The campaign needed a clear, responsive site that could communicate values, support donations, publish events, and help supporters take action.
Constraint: Campaign sites are judged in seconds by people arriving from a text message on a phone, and the content changes constantly. Anything that required a developer for a routine update would have failed in week one.
Decision: Treat the site as operational infrastructure rather than a publication. Message, donation, voter information, events, and supporter data were connected as one path, so a visitor who arrived to read something could leave having done something.

System createdCampaign pages with a responsive, mobile-first layout · Donation paths integrated into the primary journey · Voter information and event content

Read the case study — Caitlyn for Georgia 9

06Campaign website and ongoing supportLive

Scott Soracco for Georgia

A state house campaign gained a credible digital home that could keep changing as the race did.

Situation: The campaign needed stronger regional positioning, professional credibility, and a flexible place to publish interviews, events, and updates.
Constraint: A state house race is decided in a specific place. Generic campaign language would have described any candidate anywhere, and the site had to stay editable through a race that changes weekly.
Decision: Lead with place. District and regional language were clarified first so a voter could tell within one screen whether the race was theirs, and the content hierarchy was structured so interviews, events, and updates had a permanent home instead of being wedged in.

System createdCampaign website with a clarified content hierarchy · District and place language worked through the site · Integrated campaign media and interview coverage

Read the case study — Scott Soracco for Georgia

07Business to business websiteLive

ADS Integration

A technical business gained a web presence that explains its capability to the people who buy it.

Situation: The business needed a professional web presence, and coordinated access to hosting, domain, and launch responsibilities that were spread across several parties.
Constraint: Technical firms tend to describe themselves in the vocabulary of the work rather than the vocabulary of the buyer. On top of that, nobody held a complete picture of who controlled the hosting and the domain, which is the kind of gap that stops a launch dead.
Decision: Resolve ownership before design. Technical access was mapped and coordinated first, then the site was structured around clear business communication so a prospect could understand the capability without already being an engineer.

System createdWebsite foundation built around clearer business communication · Service architecture translated into buyer language · Responsive page structure

Read the case study — ADS Integration

08Owned media and brand system

Rosecraft Signal

Rosecraft built its own educational brand so that explaining the work is part of the work.

Situation: Every agency publishes a blog and almost none of them are read. Rosecraft needed an educational channel that did not sound like every other agency blog.
Constraint: The teaching had to stay useful to someone who is not going to hire Rosecraft. The moment education becomes a disguised sales page it stops being trusted, and a studio built on clarity cannot afford that.
Decision: Give the education its own identity and a stated position. Clarity Over Noise became the organising idea, and the clay founder guide gave the explanations a consistent voice that is recognisably Rosecraft without requiring Jon to be photographed for every post.

System createdThe Clarity Over Noise concept and positioning · The clay founder guide character and its usage rules · A visual language for explanatory content

Read the case study — Rosecraft Signal

02How a case study is built

Seven questions, answered in the same order every time.

If a section is missing from a case study on this site, it is because the evidence for it does not exist yet — not because it was edited out.

01
The situation
Who the client is and what was actually going on.
02
The constraint
The thing that made it hard. Usually not the thing they asked about.
03
The strategic decision
What was chosen, and what was rejected to choose it.
04
The system created
What was built, component by component.
05
Rosecraft responsibilities
What Rosecraft did, separated from what the client or others did.
06
Available evidence
What can be shown today, and what is still being cleared.
07
The outcome
Stated only when it has been measured and verified. Otherwise absent.

03Selected professional experience

Founder career work, clearly labelled.

The work below was performed by Jonathan Rose as an employee. It is not a Rosecraft client engagement and is not presented as one. It is here because the experience shapes how Rosecraft works, not to inflate the client list.

Employment, not a Rosecraft engagement
Ames Taping Tools
Marketing operations, campaign execution, and reporting for a multi-location business.
Work performed as an employee, not as a Rosecraft client engagement.
Employment, not a Rosecraft engagement
Healthcare growth and marketing operations
Growth systems, CRM structure, content, and operational marketing in a healthcare setting.
Work performed as an employee. Employer name pending confirmation before publication.

04In the queue

Projects being prepared for publication.

These exist, and they are not published yet because the permissions, images, or business context are still being confirmed. Listing them is more honest than quietly padding the grid.

K9 Inn
Scope confirmation, approved images, and a testimonial request
House of Ravenwood
Deliverable confirmation and permission
Mindful Health Counseling
Public use confirmation and accessibility work review
PAMA site
Organization name, public link, scope, and permission
Oddball Driver
Confirmation that the work can be framed as meaningful business support

05Similar situation?

Discuss a similar project.

If one of these sounds like your business — good work, unclear digital presence, systems that do not talk to each other — that is the conversation worth having. Describe what is changing and what is not working, and you will get a direct answer about fit.

Every project tellsa business story.

The decisions behind the deliverables.

Filter by type of work

Seven questions, answered in the same order every time.

The situation

The constraint

The strategic decision

The system created

Rosecraft responsibilities

Available evidence

The outcome

Founder career work, clearly labelled.

Ames Taping Tools

Healthcare growth and marketing operations

Projects being prepared for publication.

Discuss a similar project.