Armonía
An end-to-end product system for a psychology practice, shaped from discovery through daily operations and public distribution.
A solo clinical psychologist operating a private practice
2023 to 2026, including a two-year pause before the current product phase
The result
Armonía replaced an ever-growing operational spreadsheet with a dedicated system Carla now uses as her primary tool, while the public experience gives prospective patients a clear, human path to begin a conversation.
Carla uses the private Armonía application as her primary operating system.
Product cycle
- 01
Discover
- 02
Position
- 03
Design
- 04
Build
- 05
Launch
- 06
Distribute
- 07
Learn
01 / What changed
The operating model changed, not just the interface.
From an ever-growing spreadsheet to a system built around the practice.
The practice had accumulated operational data across a Google Sheet that kept growing every month. It could store information, but it offered little room to understand the business or support better decisions. Armonía moved the active workflow into a dedicated application. Carla now uses that application as her primary system, and the former Sheet is archive-only.
The former Google Sheet is now archive-only.
The practice's previous operational spreadsheet after adoption of the private application.
Source: Practice-owner operational confirmation, recorded as a public-safe summary (privately verified)02 / For whom
Two audiences. Two surfaces. One coherent practice.
One product system serves two connected audiences without pretending they use the same interface.
- Carla needs a dependable operating view of her practice, with workflows that make the growing body of data easier to use and analyze.
- Prospective patients need to understand the practice, feel the intended tone, and begin a private human conversation without navigating a complex booking system.
03 / Why this product
Research before software.
Start with the real operating problem, then connect the private and public experiences through one product intent.
I began with design-thinking interviews led with Carla, then used AI to help organize and analyze the research. The synthesis exposed a practice whose information had outgrown its spreadsheet structure. The product bet was that a dedicated operating system could create a clearer analytical space, while a distinct public experience could communicate the practice and hand interested people to Carla through WhatsApp.
AI supported the product-development workflow. Carla remained the domain expert and decision-maker, and the application itself does not claim an AI runtime.
04 / My role
End-to-end product ownership, with Carla as the decider.
End-to-end ownership with an explicit decision boundary.
I was involved across the full cycle: interview design, research synthesis, opportunity framing, product strategy, brand direction, interaction design, application engineering, cinematic storytelling, launch, and distribution. Carla contributed the clinical and operational truth, participated throughout validation, and made the final decisions.
- Product strategy grounded in Carla's operating reality
- Brand, UX, and two distinct product surfaces
- Private application and public-site engineering
- Film direction, launch story, and distribution assets
- Research and production assistance from AI, with human review and decision-making
05 / How it works
Trust begins in public. Operations continue in private.
A human public journey and a private operating application, connected by the practice rather than an automated integration.
The experience from first contact to practice operations
- 01
A prospective patient discovers Armonía through the website or shared content.
- 02
The public experience explains the practice and creates enough trust to begin a conversation.
- 03
The person contacts Carla through WhatsApp, where appointment coordination remains human.
- 04
Carla manages the practice through the private application and uses its operational and reporting views.
- 05
There is no claimed automated transfer from WhatsApp or the public site into the private application.
06 / Decisions
The choices that shaped adoption and trust.
The most important choices favored adoption, trust, and truthful operating boundaries.
Replace the spreadsheet in stages
Context
A new application would create no value if it merely duplicated a growing Sheet or demanded a risky all-at-once migration.
Alternatives considered
- Recreate the existing spreadsheet structure in a new interface
- Attempt to move every workflow at once
Trade-offs
- A staged transition takes longer to complete
- Each released workflow has to be useful enough to earn adoption
Result
The dedicated application became Carla's primary system, and the Google Sheet became archive-only.
Keep appointment intake human
Context
The first contact concerns psychological care, so warmth, privacy, and judgment matter more than an automated booking funnel.
Alternatives considered
- Public self-scheduling
- An automated intake flow
Trade-offs
- WhatsApp requires Carla's attention
- The practice retains control over a sensitive first interaction
Result
Prospective patients contact Carla through WhatsApp to coordinate appointments.
Design one practice experience across two separate products
Context
The public site and private application solve different jobs and live in separate repositories.
Alternatives considered
- Force both audiences into one interface
- Describe a technical integration that does not exist
Trade-offs
- The connection is operational and narrative rather than automated
- Each surface can remain focused on its actual user
Result
The public experience supports discovery and a WhatsApp handoff. The private application supports Carla's operations and analysis.
07 / Reaching people
A launch story designed as part of the product.
The launch system combines a public product, cinematic storytelling, useful content, and a direct call to action.
- Audience: people considering psychological support and people already connected to the practice
- Channels: the Armonía website, its blog, social content, and direct sharing
- Launch hook: a cinematic journey that expresses the emotional direction of the practice
- Reusable asset: the film and its visual language across the public experience
- Call to action: begin a conversation with Carla through WhatsApp
- Observable signal: a person reaches the WhatsApp contact path; no conversion rate is claimed
08 / Evidence
What can be shown, and what is deliberately withheld.
The story is supported by inspectable public artifacts, a documented design process, and tightly scoped operational confirmation.
Carla uses the private Armonía application as her primary operating system.
Current use by the practice owner, not a claim about patient adoption or business impact.
Source: Practice-owner operational confirmation, recorded as a public-safe summary (privately verified)The former Google Sheet is now archive-only.
The practice's previous operational spreadsheet after adoption of the private application.
Source: Practice-owner operational confirmation, recorded as a public-safe summary (privately verified)The product process moved from individual screen validation to integrated, task-based prototype validation with Carla.
Documented product-development process, not a usability metric or clinical outcome.
Source: Private engineering-process and validation documentation (privately verified)The public Armonía website is live and presents the practice and its approach.
Public product surface only; availability does not establish conversion or clinical outcomes.
Source: Armonía public websiteA production private application exists with authenticated operational and reporting workflows.
Application surface and implementation only; no patient records or private analytics are published.
Source: Private application repository and public login surface (privately verified)09 / Learning
Keep the chain from evidence to decision intact.
Traceability and adoption mattered more than feature volume.
The strongest product decisions could be traced from Carla's words to a research insight, a user story, a validation task, and finally the implemented workflow. AI made it faster to organize evidence and explore solutions, but the useful result came from keeping Carla in the decision loop.
The next iteration should continue to observe the reporting and daily operational workflows, then prioritize the friction that appears in real use. This is a direction for continued learning, not a claim that every practice workflow is complete.
Explore Armonía
Visit the live Armonía site to experience the public product and its cinematic hero.
Supporting technology
Next.js · React · TypeScript · Vite · Hono · PostgreSQL · Drizzle ORM · Clerk · Cloudflare · WhatsApp · Contentful · Google Analytics · Google Flow