About Codivine

Technology built by people who care about the result.

Codivine exists because of a specific frustration: businesses buying software from companies that never really understood the business. Plenty of technically correct systems get built that solve the wrong problem, and plenty of good ideas die in a queue behind an account manager.

So we built the company we’d want to hire: small enough that you know exactly who you’re dealing with, experienced enough to take on work that matters, and honest enough to tell you when the answer is simpler or cheaper than you expected.

Technology should solve business problems, not create more of them.

Every system we build is judged by one question: is the business measurably better off because it exists? Faster, less error-prone, easier to run, or bringing in customers it wasn’t reaching before.

That sounds obvious. It isn’t how a lot of software gets sold. It’s easy to deliver a project that hits every requirement on a list and changes nothing about how the business actually operates — because nobody checked whether the list described the real problem.

Experienced enough for serious projects. Small enough to care. That’s the whole positioning, and it’s a deliberate trade-off rather than a marketing line.

The core team

Who you’d actually be working with.

Two people, with complementary jobs: one responsible for the technology, one responsible for making sure it matches what your business needs.

Oskar Szymczak

Founder & Software Engineer

Oskar founded Codivine and is the engineer behind the technical work. He is involved in projects directly: writing code, designing architecture, and making the calls about how a system should be built and where the complexity is worth carrying.

His work spans web and mobile development, custom business software, integrations between systems, process automation and applied AI. The common thread is starting from the business problem — what actually goes wrong today, how often, and what it costs — before deciding what to build.

If you work with Codivine on something technical, you are talking to the person responsible for the result, not to someone relaying messages.

Focus

Software architecture
Web & mobile development
Business automation
AI and LLM integration
Technical SEO implementation
Product development

LinkedIn[ADD LINKEDIN URL]

Marta Szymczak

Sales & Key Account Manager

Marta leads client relationships at Codivine. She is usually the first person you speak to, and she stays involved for the length of the engagement rather than handing you over once a contract is signed.

Her background is in internet technologies, fibre-optic infrastructure and wireless connectivity, along with several years in sales and account management. That combination matters: she can hold a conversation about what a system needs to do without translating everything through a third party.

Her job is to understand the business behind the request — what you are trying to achieve, what constraints you are working within, and what a good outcome looks like — and to make sure that understanding reaches the people building it.

Focus

Client communication
Understanding business requirements
Sales and commercial scoping
Key account management
Project communication
Internet, fibre and wireless technologies

LinkedIn[ADD LINKEDIN URL]

Technology and the client relationship, side by side.

Most problems in software projects are communication problems wearing a technical costume: a requirement that meant something different to each side, a constraint nobody mentioned, a decision made without the business context. Splitting these two roles deliberately — and keeping both in the conversation — is how we avoid most of them.

Understands

What you’re trying to achieve

Owns

How it actually gets built

Scaling delivery

When the project gets bigger, so does the team.

Codivine maintains a network of trusted specialists who can join projects when additional engineering or project-management capacity is needed.

This allows us to stay lean for smaller engagements while building the right team for larger applications, automation systems and complex technology projects.

For larger projects, we work with trusted specialists from our extended delivery network, allowing us to scale the team around the actual requirements of the project — rather than building a permanent organisation you end up funding through the rate card.

Software engineering

Additional development capacity for larger applications, platforms and systems with real deadlines.

Project management

Coordination when a project has enough moving parts — or enough stakeholders — to need someone owning it full time.

Specialist delivery

Focused expertise brought in for a specific part of a build rather than kept on payroll year-round.

We don’t list specialists by name unless they’ve agreed to be publicly represented as part of Codivine. When someone joins your project, you’ll know exactly who they are and what they’re responsible for.

How we work

Six things we won’t compromise on.

The problem comes first

We ask what actually goes wrong today before proposing anything. Sometimes the honest answer is that you don't need what you came to ask for.

No layers

You talk to the people responsible for the result. Nothing gets relayed through an account manager who wasn't in the room.

Say the inconvenient thing

If a deadline is unrealistic, a feature isn't worth building, or an off-the-shelf tool would do the job, we'd rather say so early than be agreeable and expensive.

You own what we build

Code, data and infrastructure belong to you. We want to be the team you keep working with, not the team you can't leave.

Small on purpose

We're not trying to become a large agency. Growing headcount would change the thing that makes this work — that we know our clients and stay in the details.

Finish properly

Launch, migration, monitoring, documentation and handover are part of the project, not an optimistic afterthought.

Track record

Small team. Serious projects.

Being a small company is a choice about how we work with clients, not a description of what we can build.

Codivine ran as a sole proprietorship before becoming a company. The legal entity changed; the name, the person responsible and the work did not. Everything below was delivered under it.

Websites and stores delivered: 200+Websites and stores delivered
Platforms shipped to: web, iOS, Android: 3Platforms shipped to: web, iOS, Android
Products built end to end: 6+Products built end to end

Real estate technology

The area we've gone deepest in — several products for property businesses, across every platform an agency actually uses.

Web
iOS
Android

A CRM for property businesses
Built around properties, buyer requirements and viewings rather than a generic sales pipeline.
A property platform across web, iOS and Android
Including a separate client-facing site, so agents and their customers each get an interface built for them.
A second product for estate agents
Focused on the day-to-day work of running viewings and capturing the leads that come out of them.

Mobile applications

Published apps on both stores, across consumer categories with very different demands.

iOS
Android
Web

Two published mobile games
Real-time gameplay and the performance constraints that come with it — a long way from a form over a database.
A skincare app on web, iOS and Android
One product delivered across three platforms with a shared backend.
Widgets for a nutrition tracking app
Home-screen widgets for an established app with a large existing user base.

Websites and online stores

The volume work — and the reason the technical SEO opinions elsewhere on this site come from practice rather than reading.

Web
E-commerce

Over 200 websites and online stores
Built, rebuilt or repaired, for businesses ranging from single-location operations to established brands.
Brand sites for international companies
Including a global motorcycle manufacturer and consumer brands with existing design systems to work within.
SEO audits, fixes and implementation
Across a large number of those sites — the diagnosis and the code changes, not one or the other.

Client names are left out because we don’t yet have written permission to publish them — not because the work is vague. We can be far more specific in a conversation. More on the work page.

Work with the people who build it.

If that sounds like the kind of arrangement you want, the next step is a conversation about what you're trying to achieve.

Start a conversation See our services

No specification needed. A description of the problem is enough to start.