Services / remote Poland · local Wieruszów area
Web applications and integrations for businesses
I design and build web applications, dashboards, and integrations around how a business works. I work remotely across Poland and also offer local collaboration in Wieruszów, Wieluń, Kępno, Sieradz, and nearby towns.
01
Applications and dashboards
- Problem
- Teams repeat work in spreadsheets or several disconnected tools.
- Result
- One place to handle the agreed workflow, its data, and user roles.
- Scope
- The scope covers agreed flows and permissions; migrations or automation are included only when agreed.
02
System integrations
- Problem
- People copy data by hand or systems show conflicting versions of a record.
- Result
- An agreed data flow between systems, with common failures and retries considered.
- Scope
- Before estimating, we check APIs, test access, limits, and system owners. Feasibility depends on those conditions.
03
Existing product development
- Problem
- An application no longer fits the process or is difficult to extend safely.
- Result
- An agreed change built into the existing product with its actual constraints in mind.
- Scope
- We first review the code, environments, and dependencies; work outside the agreed scope is discussed separately.
04
Company websites
- Problem
- Visitors cannot quickly understand the offer or find the next step.
- Result
- A clear, responsive site that explains the services and makes contact straightforward.
- Scope
- We agree on content, materials, and features up front; larger applications and integrations are separate scope.
From scope to handover
01 / Discovery
You describe the current process, users, systems, and problem. We clarify what the first version will leave out.
02 / Scope and estimate
I check dependencies, available documentation, and acceptance criteria. The estimate follows the agreed scope.
03 / Build and review
I deliver visible pieces for review. We agree on scope changes and decisions that depend on external systems as they arise.
04 / Handover
After acceptance, I hand over the code and agreed documentation and discuss running the product. Maintenance and further development are scoped separately.
What to bring to a first conversation
Bring a description of the current process, user roles, example data without confidential information, the systems involved, and known constraints. A mockup or API specification helps but is not required for an initial conversation. Do not send passwords or access keys.
Common questions
What do you build?
- I build company websites, web applications and dashboards, and integrations between systems. I can also join an existing product to add a feature, simplify the interface, or improve the code needed for further development.
How much does a company website cost?
- The price of a company website depends on page count, supplied content, forms, and design scope. I provide a quote after we agree on scope. Apps, dashboards, and integrations are quoted separately. Content work, hosting, and maintenance are agreed in the quote.
Do you work remotely or locally?
- I work remotely across Poland. I also offer local collaboration in Wieruszów, Wieluń, Kępno, Sieradz, and nearby towns. We agree on in-person meetings or reviews when they help the project.
Next.js or WordPress for a business site?
- WordPress can make sense when a team needs to edit content often without a developer, or for a simple blog. I choose Next.js (or a similar stack) when performance, custom logic, integrations, dashboards, or longer product development matter. Technology follows the task - I do not assume one tool up front.
How do pricing and kickoff work?
- We first clarify the problem, users, and first-version scope. Then I check dependencies and acceptance criteria; the estimate follows the agreed scope. Scope changes are discussed separately. I do not assume a delivery date or business result in advance.
What should I prepare for a first conversation?
- A description of the current process, user roles, example data without confidential information, the systems involved, and known constraints. A mockup or API documentation helps but is not required. Do not send passwords or access keys.
I designed and built Bede.app myself, an invitation and RSVP application.
View the Bede.app case study