Sprawdzeni.pl: a service directory rebuilt from the ground up
The previous version made the service difficult to use
Sprawdzeni.pl was intended to connect people looking for services with companies and specialists. The earlier application did not turn that idea into a useful experience. Recurring errors disrupted the service, and adding more patches did not provide a sound basis for further development.
After taking over the project, we decided not to extend the old code. We rebuilt the application, its architecture, and its template from the beginning. We retained the visual direction originally devised by Marek Tarasiuk, the owner of Sprawdzeni.pl, but implemented and expanded the interface ourselves.
Search takes users from a need to a specific listing
The new application lets users search for service providers by service name, category, location, and distance. A listing profile can include the company description, service area, categories, and materials added by its owner.
After signing in, providers manage their own listings and statuses. A visitor can move from search results to a profile, review feedback connected with it, and start a conversation about the selected service.
Legacy data needed verification, not just migration
Some listings came from the previous version, but much of the data was no longer current. A straightforward import would have carried the same problem into the new system. We therefore connected the application to the Polish CEIDG, REGON, and TERYT registers and built an email and SMS campaign module.
The first mailing provided GDPR-related information. Contact with the companies also helped establish which entries were still current. The rebuild therefore covered not only the code, but also the way the listing database was maintained.
Reviews, messages, and moderation work as one process
Reviews are linked to specific listings. A profile owner can ask a customer for feedback, while visitors see that feedback in the context of the selected provider. Messages also remain tied to a listing, allowing users to move directly from finding a company to discussing a service.
Listings, reviews, and uploaded files enter the moderation panel. A moderator can accept them, reject them, or leave them for a later decision. Automated moderation also ran in production and supported the handling of incoming content.
The service gained promotion and communication tools
We implemented paid listing promotion through PayU. The campaign system could contact users by email and SMS, while the panel connected these activities with listings and company data.
These features were not left as unused code. The owner confirmed that they operated in the production version of the service.
Result: a working system and clearly improved organic visibility
After the rebuild, Sprawdzeni.pl began to handle its core process correctly: publishing and finding listings, collecting reviews, enabling user contact, and moderating content. The owner also observed a clear improvement in organic visibility.
We do not state a percentage increase or visitor count because no approved measurement from that period is available. The service still attracts noticeable traffic, although no regular SEO work followed the main implementation. The owner is now considering a refresh and further development of the system.
Client feedback
I had the opportunity to work with many developers, but this was the first time with someone so reliable, competent, and consistent with deadlines. I definitely recommend the cooperation.
Marek Tarasiuk, owner of Sprawdzeni.pl
When does a similar rebuild make sense?
Rebuilding an application from scratch is not always the right decision. We first assess the code, data, integrations, and processes that must remain available. A rebuild makes sense when further fixes preserve the problems of the old architecture, key features remain unstable, and every new development step has to work around the same constraints.
Sprawdzeni.pl also highlighted another important issue: new code does not automatically repair old data. If a database contains outdated entries, the rebuild plan must include a way to verify, complete, or safely withdraw them.
Let us discuss your existing application
If your system regularly runs into errors or prevents further development, describe its main process, most serious problems, and the parts that must be retained. We will assess whether the better route is a repair, replacement of a selected module, or a complete rebuild.