Apps and websites that take work off your team.
From a simple website to a custom system. I run the project from the first conversation about your process to post-launch support. The project, its data and documentation remain at your disposal.
- 10+
- projects delivered end-to-end
- 5
- steps from message to support
- <24h
- typical response time
- day 1
- access to code, data and docs
What companies come to me with most often.
Each item is a problem I hear on the first call, and what you get in return. The technology comes last, because it's a tool, not the product.
- Excel and email stopped being enoughA panel where the team runs the contract and document workflow in one place, with a change history and permissions. LARAVEL · VUE
- Appointments booked over the phoneA booking system where the client picks an open slot themselves, and you see how booked up you are. LARAVEL · LIVEWIRE
- The site can't be changed without a developerA site on a lightweight, custom CMS where you edit content and photos yourself. No plugins, no yearly licences, no updates that break the layout. CUSTOM CMS
- Off-the-shelf software doesn't fit your processAn application built around how your company actually works, instead of workarounds that cost more than the software itself. PHP · VUE 3 · NUXT
- Data retyped by hand between systemsA connection that does it in the background: warehouse, accounting, a partner's system. Plus chatbots and AI agents wherever someone answers the same question for the hundredth time. OPENAI · MCP · REST · SOAP
- You want to sell your softwareArchitecture that can carry it: modules turned on per client, separate production instances, subscription billing. FEATURE FLAGS · BILLING
- The system runs, but nobody wants to touch itAn upgrade on a live system, with no downtime. From older, unsupported versions of PHP and Laravel to current ones, with tests, so you know nothing broke. PHP · LARAVEL · TESTS
- You have nobody to call when something breaksMaintenance: monitoring, backups, updates and fixes. Including systems built by someone else. DOCKER · CI/CD · PHPUNIT
Don't see your case here? Write anyway. Many projects are a mix of a few areas.
From a simple site to a system.
Three levels of engagement. Not every company needs the third one, and plenty of cases close at the first.
-
Simple website
A few pages, a CMS you edit yourself, a contact form, basic SEO and accessibility. For a company that needs a credible presence online and nothing beyond that.
-
Website with features
Everything above plus one or two things that genuinely save time: booking a slot, a client panel, a quote calculator, an integration with a system you already use.
-
Custom system
A tool built around how your company works, from the data model to deployment and maintenance. For when off-the-shelf software forces you to change how you work instead of supporting it.
Not sure which level? Write to me. I'll tell you which one you actually need, not which one I'd like to sell. Sometimes the answer is: you need something simpler than you think.
From the first message to support.
- You writeA few sentences about what needs to start working differently. I usually reply within 24 hours.
- A callThirty to forty-five minutes about the process, not the technology. I tell you straight whether I can help.
- Scope and estimateA written scope, a range and a timeline, before I start anything.
- DeliveryI work in stages. After each one you see a working version, not a presentation.
- SupportFixes after launch and maintenance, if you want it. You have access to the project and its data from day one.
- Process first, code second. Before proposing anything, I want to understand where the business loses time.
- Boring technology wins. Laravel, MySQL, Redis: a proven stack that runs for years, instead of architecture for show.
- Smallest scope that solves the problem. If something simpler will do, I'll say so instead of building a system you don't need.
- No lock-in. The project, its data and documentation remain at your disposal.
What I can build.
The areas I work in day to day. Technology is a tool here, so I describe it by what it makes start working.
- Billing and subscriptions
Subscriptions, recurring invoices and e-invoices sent straight from the system to the national e-invoicing service. Modules switched on per client, so one system serves different plans.
- System integrations
REST, SOAP and webhooks, including the Booking.com Taxi API. Prices calculated in real time on request from a partner system, plus data kept in sync without manual retyping.
- Sites fed by external data
Pulling data from other people’s systems, with caching and rate limiting so the site holds under traffic spikes. Editors run content in several languages on their own.
- Internal panels and apps
Document workflows, permissions, change history, mobile and SMS notifications. Built around how the company actually works, not around a template.
- Modernisation and maintenance
PHP and Laravel upgrades on live systems, with no downtime and a safety net of tests. Monitoring, backups and fixes, including for systems built by someone else.
- Accessibility and quality
WCAG 2.1 AA, functional and E2E tests, Docker and CI/CD. Changes ship without breaking what already works.
One person, the whole project.
Łukasz Cysewski, a fullstack developer from Gdynia, Poland. Over three years of commercial work on SaaS platforms and client websites. Backend, frontend and infrastructure in one pair of hands, with no handoffs between departments.
Before I started working commercially, I taught kids how to code. That's where I picked up the habit of explaining technical things in plain language. Full technical profile.
Before you write.
The questions that come up most often on a first call.
-
How does working together start?
You write a few sentences about what you need. I usually reply within 24 hours and tell you straight whether I can help. Then a call about the process, an estimate for the scope, delivery and support after launch. I run projects end-to-end, with no handoffs between departments.
-
How much does a project cost?
There is no off-the-shelf price list, because an estimate depends on scope. I work B2B and invoice with VAT: either a fixed price for a defined scope, or a day rate for longer engagements. You get a range after the first call, before we start building anything.
-
What does the estimate cover?
A written scope: what gets built, what doesn't, how many revisions are included in the price, and what happens when a new idea comes up along the way. The estimate covers deployment to the server and handing over access. It doesn't cover things you buy directly: hosting, the domain, paid integrations, photos.
-
Who handles the design and UX?
I'm a developer, not a designer. On simpler projects I work with my own polished layout, like this site. When the look matters a lot, I bring in a designer from people I've already worked with, or work from a design supplied by the client. I bring this up on the first call, so there are no surprises.
-
Who maintains the site after launch?
It's up to you. You can take over everything, because you have access to the project, its data and documentation from day one. You can leave maintenance to me: monitoring, backups, updates and fixes at an agreed level. Or you can hand it to someone else.
-
How much does hosting and maintenance cost?
You buy hosting yourself, directly from the provider, and you pay them, not me. A simple site fits on cheap shared hosting; an application with a database, queues and cache needs a VPS. I give you the exact cost and a provider recommendation in the estimate, so there are no surprises after launch.
-
Do you work remotely or on site?
I am based in Gdynia, Poland and work remotely with clients across the country. On-site meetings in the Tricity area when a project calls for it.
-
Will you take over a system built by someone else?
Yes, that is a common scenario. I have run PHP and Laravel upgrades on live systems, from older, unsupported versions to current ones, with no downtime. I start with a review of the code and infrastructure so I can tell you straight what can be saved and what has to be rewritten.
-
Who owns the code after the project ends?
Code and data created specifically for your project remain at your disposal. You receive access to the project, data, and documentation required to maintain and further develop it.
If the website uses my custom CMS, its core code remains my intellectual property. You receive a perpetual right to use the CMS as part of your website and are not dependent on continuing to work with me.
-
How fast do you reply?
Usually within 24 hours, faster on working days.
-
Do you build AI integrations?
Yes. Integrations over REST, SOAP and webhooks, OpenAI models and my own MCP servers. After hours I build a tool where an AI agent gives saved links a title, a summary and a category, and my own CMS has an OCR component that turns photos of documents into text.
-
Do you take ongoing contracts or only one-off projects?
Both. A single project to deliver, or an ongoing B2B contract with an agreed number of hours.
Write.
B2B collaboration: a project to deliver or an ongoing contract. VAT invoice, remote or on-site in the Tricity area. Describe what you need in a few sentences. I usually reply within 24 hours and tell you straight whether I can help.
Looking for a candidate rather than a contractor? Technical profile and GitHub.
- kontakt@lukaszcysewski.me
- Phone
- +48 511 599 056
- Base
- Gdynia · remote