Christopher Bengtsson

Available for smaller, clearly scoped projects

← All capabilities

Services · Focused assignments

Get a clear second opinion on your software.

Before a launch or a technical change, you may need help understanding what deserves attention. I review a defined part of a codebase, an integration or an architecture proposal and explain the findings in practical terms.

Gothenburg · Sweden · Remote

Ways I can help

Start with a concrete need.

  • Review a proposed change

    Examine how a feature or integration fits the existing system, including dependencies and likely failure cases.

  • Assess an existing application

    Look at an agreed user flow or code area for correctness, maintainability and gaps in testing.

  • Review an AI-built first version

    Understand what is implemented, what remains incomplete and what needs attention in the agreed scope before the next step.

Give the review a question to answer

A useful review starts with a decision: can we release this flow, how should these systems connect, or why is this area difficult to change? We agree which code, configuration and supporting material are included.

The review can cover interfaces, backend services, data handling and their boundaries. Access controls and credential handling can be part of an engineering review, but the engagement is not a certification or a comprehensive penetration test.

Findings you can act on

You receive a written summary with prioritized findings, references to the relevant code or behavior, and recommended next steps. I distinguish observed issues from questions that require further investigation and explain the limits of what was reviewed.

Illustrative finding — medium priority: when a CRM request fails, the form displays a success message even though the record was not saved. The user may believe the task is complete and lose the information they entered. This is a fictional example showing how a report can describe an issue.

Recommended change: show success only after confirmed acceptance, preserve the entered values when delivery fails and give the user a clear retry action. Verification: test an accepted request, a rejected request and a timeout, including whether retrying can create a duplicate. The report would reference the relevant code and distinguish reproduced behavior from untested assumptions.

Implementation can be scoped separately once the findings are understood.

From first question to handover

  1. Describe the change

    Tell me what exists, what you want to achieve and any deadline. A reproducible problem or a concrete example helps us start.

  2. Agree a scope

    We identify the deliverable, the access needed and how to check that the work is complete. I confirm availability before we agree a schedule.

  3. Build or review

    I work within the agreed scope and explain findings or tradeoffs. If new work emerges, we discuss it before extending the assignment.

  4. Hand over

    You receive the agreed changes or findings, with practical notes on what was checked and what needs attention next.

Experience

Experience behind the approach

My background spans interfaces, services, data and integrations, including KYC/Salesforce work at Trustly and ownership of a change-request portal in a consulting assignment. That experience informs how I examine the boundaries between parts of a system.

See selected work

Mentioning these organizations does not imply that they endorse my independent services.

Questions before we start

Can I commission a review without a technical background?

Yes. Describe the decision you need to make and what the software should do. I explain the findings in plain language while keeping technical references useful for whoever implements the changes.

Will you also fix the issues?

I can help with agreed fixes if the scope and availability fit. The review and any implementation are separate deliverables, so you can decide how to proceed.

Can you guarantee the application has no bugs?

No. A review covers the agreed material and checks. The report identifies what was examined, what was found and what remains outside the scope.

Contact

Tell me about your project

Tell me what decision you need help with, what exists today and which part of the software you want reviewed.

[email protected]

Thank you! Your inquiry has been sent.

Read how I handle your personal data: Privacy information.