Rafael's own independent practice
This is not external client work. It is the platform used to explain, estimate and begin Rafael Pinto projects.
OWN BUSINESS PLATFORM · LIVEDigital services2026
Rafael Pinto
Platform.
A service platform connecting positioning, guided pricing and the project brief so small-business buyers can understand scope before they enquire.
AT A GLANCE
The project in four answers.
Buyers need clarity before a sales conversation
A small website and a system with accounts or operational workflows cannot be presented as the same product or price.
A connected route from service to brief
Positioning, deterministic pricing guidance, project classification and Start Project handoff work as one buyer journey.
Live with protected delivery systems
The public journey is operating. Quantitative conversion results are not yet claimed.
THE BUSINESS PROBLEM
Show an accessible starting price without hiding complexity.
Small-business buyers often know the problem they want solved but not whether it requires a normal website, a booking or quote journey, or custom software. A low headline price can attract attention, but it becomes misleading if an account-based platform appears to cost the same.
The platform needed to explain the difference early, give useful guidance without a technical quiz and preserve enough context for a personally reviewed brief.
CONSTRAINTS & SCOPE
Clarity across public and protected journeys.
- Website entry pricing must remain accessible and visible.
- Advanced portals, apps and SaaS products need a separate custom-software classification.
- The estimator provides guidance, never an automatic final quote.
- Visitors can see a range without creating an account or paying.
- Estimator choices must survive the handoff into Start Project.
- Client, Admin and payment experiences remain authenticated and are not exposed as public evidence.
RAFAEL'S ROLE
Product, interface and delivery considered together.
Rafael directed the product, structured the information architecture, designed the public and protected journeys, implemented the interface and integrations, and defined the QA and ongoing Care model.
APPROACH & KEY DECISIONS
Four decisions that protect buyer trust.
- 01
Separate websites from custom software
Problem: one package ladder can understate complex work. Decision: classify portals, apps and multi-user systems separately. Effect: the early range better reflects the type of build.
- 02
Keep pricing deterministic
Problem: generated pricing can be inconsistent. Decision: use calibrated rules while language assistance only helps classify the brief. Effect: the same requirements produce the same guidance.
- 03
Preserve the buyer's work
Problem: repeating selections creates friction. Decision: carry the chosen project route and relevant context into Start Project. Effect: the enquiry begins with a more useful brief.
- 04
Keep the final decision personal
Problem: a calculator cannot see every constraint. Decision: label the estimate as guidance and require personal scope review. Effect: unusual work remains reviewable before commitment.
WHAT WAS BUILT
One platform across the client relationship.
Service positioning
Responsive public pages explain websites, systems, apps, ongoing Care and the business problems each route addresses.
Guided estimator
Calibrated project categories and options create an indicative range while preserving a personal final-scope boundary.
Start Project journey
Saved pricing and project context move into a concise brief without requiring an account or payment first.
Protected client operations
Authenticated quote, approval, payment, project and Care architecture supports the relationship after enquiry.
RESPONSIVE EXPERIENCE
The buying journey
across real screens.
The desktop pricing page and mobile Start Project route were captured from the live public platform. Protected client information is not shown.
TECHNICAL DELIVERY
Static-first where public. Protected where required.
Public pages use clean, crawlable URLs and a deliberately light static foundation. Interactive modules add the estimator and handoff without turning core content into a client-rendered application. Authenticated delivery, payments and operational data remain behind their existing protected boundaries.
OUTCOMES · UNMEASURED
What has been delivered.
- The service platform is live on its public domain.
- Website and custom-software enquiries are classified separately.
- Indicative pricing is visible before contact details, account creation or payment.
- Pricing context can be handed into Start Project.
- Protected client, quote, approval, payment and Care journeys have been implemented.
- A first-party measurement baseline exists; no conversion uplift is claimed yet.
LEARNINGS & NEXT PHASE
Measure whether clarity improves the brief.
The next meaningful measures are estimator completion, Start Project handoff and the proportion of submitted briefs classified correctly before personal review. Those signals are more useful than publishing an isolated traffic number.
A SIMILAR PLATFORM?
Build a clearer customer journey.
Start with what the customer needs to understand, decide and send—not with a list of technologies.