Sergio Hurtado

05 · Projects

Presente

Presente – Elderly care service

2026 · Elderly care service · Cali, Colombia · ES / FR / EN

The request

Presente supports older people in Cali, at home or in a shared house, and opens in 2027. The site had to measure real interest before opening, without promising a place that does not exist yet, across three audiences: families in Cali, children living abroad, and cuidadoras looking for work.

The solution

I refocused the site on a single indicator: the qualified expression of interest. One form whose first question, "Who are you?", shapes what follows, mobile first, with WhatsApp as a second channel and three languages. I delivered the scoping, the mockups in Claude Design, the design system artefact and the site built in PHP with Claude Code.

Analysis

Three audiences, three motivations that don't overlap. Families in Cali looking for a solution now. Adult children living abroad, who decide at a distance and who pay. And cuidadoras looking for work. A conventional brochure site serves one and loses the other two.

Before opening, a visit measures nothing at all. The only indicator that really commits anyone is the qualified expression of interest: who you are, and what exactly you expect.

Design

One site for both forms. Moving from home care to the shared house is a family decision, not a change of supplier. The architecture places them side by side, one page per form and one shared page of commitments, so the switch doesn't mean starting over.

Mobile first, WhatsApp as the second channel. That is the real ground in Colombia, not a stylistic preference: form and conversation have to be equally reachable, from the same screen.

Home on desktop. Both forms of the service fit in the opening sentence, and the two actions, registering interest or applying, stay in the header on every page.
Mobile home, Spanish by default. The headline names both forms of the service in one sentence, before any explanation.
The shared house: scale given in places, not in promises.
“Our way of working”: the service's commitments, shared by both forms.

One form for three audiences

The first question asked, “Who are you?”, isn't administrative: it branches the three or four questions that follow. A family in Cali, an adult child abroad and a job applicant never have to answer the same things, and none of them should have to read the other two's questions.

The form on desktop. Name, WhatsApp, then “¿Quién es usted?”: that answer decides which questions come next.
Expression of interest: what is not asked is written above the first field.
Applying: duration stated before the click, WhatsApp as the second option.
  • No ID, no documents, no money. The sentence sits above the first field. In this market a form asking for the cédula reads as a risk, and the sentence that says so is worth more than one field fewer.
  • “Two minutes, no documents” under the apply button: the duration is announced before the click, not discovered on the next screen.
  • Commitments written to be claimed. One page states the service's rules, identical in both forms, and says explicitly that they exist to be held to.
  • An opening “during 2027”, with no date and no address. Announcing less protects the launch: nothing to retract, and the wait stays honest.

Evaluation & iteration

The site is trilingual by structure, not by translation bolted on afterwards: Colombian Spanish by default, French and English for the diaspora, with visitor language detection. The typefaces, a display serif and a reading sans, were chosen to hold up at large sizes. A share of the readers is over seventy.

The production chain

The whole project ran through Claude, from the analysis to the code that was handed over. That is also what made a trilingual site with its own design system workable for one person.

  • Claude Cowork for the analysis. That is where I worked through the user profiles and their needs: the cuidadora looking for work, the adult child abroad deciding from a distance, the family in Cali looking for a solution now. The branching form comes straight out of it.
  • Claude Design for the mockups. Wireframes of the mobile screens first, reworked until the architecture held, then the move to high fidelity and the iterations on colours, typefaces and spacing.
  • Claude for the design system artefact handed to the client: colours, typography, spacing, corner radius, shadows, sizes, opacities, components and assets.
  • Claude Code for the build, in PHP, following the design system, delivered to the client.
Wireframes in Claude Design. Everything gets settled there, before the first colour decision: what each screen has to say, and in what order.

The artefact isn't a pretty component sheet. Every element comes with its usage notes: when you use it, when you don't, and which class matches what in the code. That is what lets the build keep moving without coming back with a question on every screen.

Components delivered with their usage rules: two tinted surfaces per view at most, and never one inside another.
Colours are named by role, not by hue, and each one carries a note saying what it is for and where it isn't.

Before opening, the deliverable isn't a website. It's a list of people waiting, and the proof that you know which ones.