Where the interaction
is the product.

A marketing site is judged on the first ten seconds. An application is judged on the four hundredth use, with a year of accumulated data, by someone doing their job under time pressure. That difference changes almost every decision, and it is why applications built like marketing sites feel wrong within a month.

The states nobody demos are where the work is. What the screen shows before any data exists, what it shows while loading, what it shows when a request fails, and what it shows when a list that was designed for twelve rows contains nine thousand. These are not edge cases; they are the majority of what a real user encounters over a year.

Authentication and roles are structural rather than cosmetic. Who can see what, who can act on what, and what is recorded when they do — decided at specification, because permission models are among the more expensive things to change once data depends on them.

What you get

• Authentication and role-based access control
• Interface built for real data volumes, not demo data
• Empty, loading, error and permission-denied states designed
• Audit trail where actions need to be attributable
• Deployment, monitoring and written handover

Not included

• Copywriting and photography
• Paid media and ad management
• Ongoing content updates unless retained