romanszopa.pl, reimagined.

'SAP Commerce Cloud Developer' is accurate and keyword-useful, but it doesn't communicate seniority or outcome. Something like 'SAP Commerce Cloud Lead Developer — B2B & B2C platforms for enterprise clients across Europe' would immediately signal both calibre and market without adding clutter.

The four 'What I do' sections — Commerce Cloud, Java backends, Upgrades, Technical leadership — are presented as bare headings with one-line descriptions. A client reading this doesn't know what problem Roman solves for them, only what Roman knows. Reframing each around a client pain point ('Your platform is falling behind? I lead on-prem to CCv2 migrations...') would change the register entirely.

Enterprise clients and agencies looking to hire a contractor want to know if Roman is available, whether he works remotely, and roughly what engagement looks like. The complete absence of this information means every visitor has to take an extra step before they can even decide whether to pursue contact.

Sending all inbound leads to LinkedIn means Roman has no control over the conversation, no way to capture enquiries from people who aren't logged in, and no data on who visited. A simple contact form with two or three qualifying questions (project type, timeline, stack) would capture more leads and pre-qualify them.

The page has no button, no link, no prompt to act until the very bottom. A visitor who arrives, reads the About paragraph, and doesn't scroll all the way down has no nudge to do anything. A single anchor link — 'Available for projects — get in touch' — placed near the top would meaningfully improve contact rates.

Even experienced buyers of technical talent have anxiety about starting the conversation. A one-sentence explanation of the process ('I'll review your brief and respond within two working days') reduces that hesitation and signals professionalism.

Roman currently has no structured way to receive a brief. A short enquiry form that captures stack, scope, and timeline could automatically filter enquiries, send a confirmation, and even flag good-fit projects — removing the manual back-and-forth that typically eats up unbillable hours.

If Roman genuinely uses AI tooling in his day-to-day SAP Commerce Cloud work, a short article or even a paragraph explaining the approach would attract search traffic from other developers and from technical buyers researching what modern SAP development looks like. It would also substantiate the claim rather than leaving it floating.

A developer working across B2B and B2C platforms in five countries almost certainly has opinions on SAP Commerce Cloud upgrades, CCv2 gotchas, or microservices integration patterns. Even two or three short technical posts would drive organic search traffic from decision-makers and developers who influence hiring — with no ongoing effort once published.

The site references customers in Poland, Czech Republic, Norway, Finland, and Sweden, but provides no specifics. Even anonymised outcomes — industry, platform version, what was delivered, what improved — would give a procurement manager or CTO something to hold onto when making a hiring decision.

An 18-year career almost certainly includes clients willing to provide a quote. A single strong testimonial from a Scandinavian enterprise client, for example, would carry significant weight and confirm that the European track record is real.

A professional photograph is a good start, but it's the only signal of personality or working style on the page. A short note about how Roman prefers to work — async, documentation-heavy, embedded in a client team — would help the right clients self-select and reduce poor-fit enquiries.

Listing Git, Maven, SQL, and REST alongside more specialised skills like SAP Commerce Cloud and Project Reactor dilutes the signal. A technical buyer already assumes a senior Java developer knows Git. Trimming this list to the genuinely differentiating technologies would make the page read as more senior, not less.

The page is a single column of text with no visual hierarchy beyond headings. A buyer who lands here and scans for 30 seconds has no clear path: no summary of value, no social proof block, no contact prompt. Small layout changes — a brief value statement, a testimonial pull-quote, a contact anchor — would guide the eye without requiring a redesign.