UslugeHR

A three-sided marketplace kept honest by a test suite that walks the whole sitemap.

Type
Product
Industry
Marketplace / services
Platform
Web application
Role
Design, build, deploy
Status
Live today: Croatian services marketplace with free tools (calculators, telecom comparison, price guides)
UslugeHR service provider listing

What made this hard.

A services marketplace built to connect customers with providers: browse services, request a quick quote, book, and pay online, while providers manage profiles and respond to enquiries and admins moderate the lot.

Two-sided marketplaces are really three products (customer, provider, admin) sharing one database. Every feature multiplies: a booking state change has to be right from three angles, and the bug you don't see is always in the role you don't use daily.

Manual testing doesn't scale to that, and neither does a unit suite that never opens a page.

What we built.

  • Built a full-site browser audit harness that walks every sitemap URL at desktop and mobile widths, exercises authenticated role journeys with temporary fixtures torn down afterwards, and drives the calculator APIs end to end. A durable site-health spec stayed behind as the regression seam.
  • Gave every non-hidden control a programmatic accessible name, and committed an accessibility spec that also asserts no duplicate IDs. A mobile sitemap tracer caught a real horizontal-overflow bug.
  • Moved the Content-Security-Policy into the repository instead of ad-hoc server edits, then replaced a third-party CDN chart dependency with a locally bundled one built through an admin-only Vite entry, which let that CDN allowance be removed from the policy entirely.
  • Made report queries portable between MySQL and SQLite specifically so the reporting page could have real feature-test coverage.
  • Fixed and regression-tested a set of genuinely instructive bug classes: a framework default not applying to a present-but-null request parameter, guarded role attributes silently dropped on creation, and notification mailables using the wrong render method so markdown mail components had no hint path.
  • Extracted duplicated lead-capture fields from several forms into one anonymous Blade component with a documented contract: the caller supplies an ID prefix, product-specific fields stay with their own templates.
  • Added an AI loan assistant on the /krediti pages for signed-in, verified users, with a consent step, throttled usage and a dated facts snapshot. Its answers are informational and not financial advice; the final decision stays with the bank.

What it runs on.

Chosen to be maintainable for years, not to win an argument on the internet.

  • PHP 8.2+
  • Laravel 12
  • Alpine.js
  • Tailwind CSS
  • MySQL
  • Stripe
  • Mailjet
  • Playwright
  • Vite

Where it landed.

The marketplace carries the full lifecycle: customer, provider and admin roles, bookings that move confirm complete, reviews, messaging, moderation, Stripe payment intents, plus a suite of financial and service calculators.

The audit harness is the part that made the rest sustainable: on a product this wide, the test suite walks the site so nobody has to.

Need something in this territory? This is Custom web app development work. Start from all services or see pricing.

Your project

Tell us what you're building. We reply within two business days.

Hour Blocks from $180reply within two business days Start a project