My business · Updated Sep 7, 2026
ruizTechServices
My tech services business website: recognizable customer problems, a shared service catalog, and an inquiry form that collects context before work begins.
See the work
From the live product
Screens captured Sep 7, 2026
Open full screenshot in a new tabServices come from one catalog
A typed service configuration supplies active offers to the homepage, navigation, and dedicated service pages. Scope, deliverables, and exclusions stay together.
Read the service catalog sourceThe inquiry asks for useful context
The live form asks for the issue, preferred support, urgency, and optional budget. Its server action assembles those fields into a Supabase inquiry record.
Read the inquiry action sourceThe context
The site is the public entry point for my local tech services business. It connects a visitor’s everyday problem with a service explanation and a request for help.
The problem
A visitor may know that a printer, computer, or connection is failing without knowing which technical service to request. The site needs to start with their problem and gather enough context for a useful first conversation.
Constraints
Service scope varies by the issue. Offers need explicit deliverables and exclusions, while the visitor-facing language needs to be understandable to people without a technical background.
The approach
Lead with common problems, separate home and small-business use cases, and explain the steps from inquiry to a scoped visit. A structured form collects the issue, support preference, urgency, and optional budget.
Architecture
A Next.js App Router site uses React components and a typed service catalog. The same catalog supplies active offers to the homepage, navigation, and service pages. A server action formats contact and qualification fields into a Supabase inquiry record.
Key decisions
Keep service definitions in one typed configuration so price, scope, deliverables, exclusions, and calls to action can be reviewed together. Separate the service offer from this personal portfolio. Ask for the problem and practical constraints before proposing work.
What it delivers
The live homepage presents eight common problem categories, home and business entry points, and a Request Help action. The source connects active service definitions to public pages and includes an inquiry action that writes the submitted context to Supabase. These are implementation outcomes; no sales uplift is claimed.
Where it stands
Active business website. The public pages and matching source were reviewed on September 7, 2026. Contact submission delivery was not exercised during this case-study review.