International Society of Breast Pathology
The International Society of Breast Pathology connects breast pathologists worldwide through collaboration, education and a shared standard of practice. Its members exchange difficult cases and second opinions, learn emerging techniques, and support the next generation through trainee awards and fellowship training.
Desktop
MobileWhat we built
A professional society lives or dies by its membership experience. Joining has to be quick for busy physicians in many countries, and the benefits have to be clear and available the moment they sign up. The site also had to look the part. It represents a rigorous medical specialty to its own practitioners, so the design needed to be restrained, credible and exact.
We built the site around membership. A Join page explains what members receive, and an online checkout lets a pathologist anywhere in the world sign up and pay in one sitting. A member login then opens the protected side of the site, where recordings of past webinars are available on demand.
Education is the society’s main offering, so webinars have their own section, with live sessions announced on the site and recordings added afterward for members. The structure is ready to grow, with room for a case study library as the society expands its teaching material.
The public pages make the case for the society itself. They set out its four aims of collaboration, access, recognition and advancement in clear language, and present breast pathology as the demanding discipline it is. The design is clean and quiet, in keeping with the profession. Wicked Code hosts the site and keeps the membership system running.
We ended up with a complete membership platform for a specialist medical society. New members can join in minutes, existing members have a single place for their education, and the society has a professional presence that matches the seriousness of its work.
AI wrote most of the code. Thirty years decided what to write.
The difference from a "vibe-coded" app is everything after step one.
Spec first, with AI as a sparring partner
We wrote the product spec and data model with AI, pressure-testing edge cases (what counts as a closure? what about partial hours? where does the data come from?) before a line of code existed.
AI-assisted build, engineer-reviewed
Features generated with AI coding tools, then read, tested and corrected by us. Every commit reviewed by a human who has shipped production software since 1997.
Data pipelines with guardrails
Closure data comes from multiple sources in multiple languages. AI helps normalise it; validation, logging and fallbacks make sure a bad feed never becomes bad advice on the water. Report back to admins if an API fails.
Deployed on our managed EU hosting
Monitoring, backups and patching on the same hosting we offer clients. Built in weeks, not months, and still ours to run and improve.
What AI did. What we did.
AI
- Generated the bulk of the application code
- Wrote first-pass tests and documentation
- Produced UI variants to choose from
Wicked Code
- Decided what to build and what to leave out
- Reviewed, corrected and hardened every piece
- Designed the data validation and failure modes
- Hosting, monitoring, and answering the phone
We'll build your product the same way.
AI-assisted from the spec onward, reviewed and hosted by people who've done this for three decades. Tell us the problem; we'll tell you honestly whether AI belongs in the answer.
Scope a build
