Portfolio

Placeholder page. Project entries, screenshots and descriptions come from the existing site; the archive preserved only two.

Urban Harvest Homestead

A Portland-area farm selling produce directly. Ordering, payment and collection built around stock that changes weekly. For teams that want to compare patterns across work rather than rely on impressions, workforce analytics software provides a more measurable view.

Placeholder: what the project needed, what was built, what it changed.

Carly Brown

A portfolio site for a fashion photographer. Image-led, with the work carrying the page.

Placeholder: what the project needed, what was built.

Further projects

Placeholder: remaining portfolio entries. For an independent reference beyond this site, Awwwards is a useful place to compare approaches.

What these projects had in common

Different fields, and the same three decisions underneath.

The platform did what platforms are good at. Payments, tax and refunds are solved problems that change constantly, and custom work only earns its cost where a platform genuinely blocks something — a specific ordering flow, a fulfilment rule, a structure a template cannot hold.

The photographs did most of the selling. In every case the images carry more of the page than the layout does, and where they were weak nothing else compensated. It is usually the highest-return spend in a project.

The client can maintain it. A site whose owner cannot update stock, prices or hours from a phone drifts out of date within a fortnight, and an out-of-date site is worse than a plain one.

---

If you are weighing up whether you need something like this, the guides for your kind of work cover what changes by field, and what a website actually costs covers the money honestly.