Write to us through the form or Discord and describe the project in a few sentences. We will reply with questions, and the quote and initial scope come back within an hour.

I have no specification. Is that a problem?

No. Most clients come with an idea. On a call we agree the scope and priorities, then write them down in a document that becomes the basis of the quote.

How do we communicate during the project?

On a project channel on Discord or Slack, with a weekly progress summary. When something needs a quick decision, we set up a short video call.

Do you meet in person?

Yes, for bigger projects we travel to the client: in and around Kraków and in larger cities. Day to day we talk through the project channel and video.

Yes. On request we sign a confidentiality agreement before we discuss the project in detail.

Who do I talk to during the project?

With the person who writes your code. We have no salespeople or middlemen, so a question about a feature, a date or a bug goes straight to the developer.

When will I see the first results?

A test version runs from the first days of the project, at a separate address. You check every stage on it before it reaches production, and once a week you get a summary: what was done, what is next and which decisions are needed.

Goals, content and materials delivered on time, decisions and acceptance of each stage, and access to the accounts held by your company. The quote, the plan, the build, the test version, the release and the documentation are on us.

What do I get at the end of the project?

The code in a private repository or an archive, with its history and no licence locks. After acceptance and full payment the economic copyright passes to you, and the warranty written into the order runs from acceptance, 90 days as standard.

Can the scope change along the way?

Yes. Both sides confirm a scope change in writing together with the new price and date (terms, clause 3.3), and the confirmed change goes into the project's documents in the panel.

Does anyone outside VulCode work on the project?

We do visual design with our partner agency Aphrodi, and our terms allow us to use subcontractors for some work. Responsibility for the project and contact with you stay with us.

How fast do I get a quote?

We reply to your message within an hour, with questions or straight away with a quote. The quote is free and commits you to nothing.

Working with us: process, pricing and contracts

What working with us looks like from the first message: who runs the project, prices and quotes, billing models, the contract and code rights, staged payments, the warranty and care after launch. Every topic has its own page with the details, before you ask.

Services

The Schedule tab of a project in the VulCode client panel: the project's stages with a description and a date

Everything about working with us on one map

Each page of this section covers one moment of a project. Find the stage you are at and start with its page.

Before the start

Working with usThe questions people ask before signing, and the pages that answer them, are in the next section.

Quote and order

The build

Payments and invoicingPayments in stages written into the order.

Acceptance

WarrantyThe period runs from final acceptance. What we fix at no cost and how to report a bug.

After launch

Maintenance and supportHosting with monitoring, updates and development after launch.

Questions before you sign

The questions asked most often before a project starts, each with the shortest answer and the page with the details.

Before you sign

The working-with-us pages summarise the rules. The terms of service and the order for your project are binding.

Client reviewsWhat clients say, with the source

What you get along the way

In every project, from a one-page site to a panel with payments, you see the progress yourself. This is how what appears in the client panel spreads over the stages of a project.

Where you see it

Onboardingthe account and the project channel
Prototypethe interface before code
The buildon the test version
Testingand final acceptance
Releasewith the code handover

Information
The link to the test version and how much of the project is paid.
The test versionat a separate address, from the first days
Reports
Acceptance and the project handover, written down in the panel.
The project handoverthe repository, documentation and access
Chat
You raise questions and notes right in the panel.
Talking to the developerthe person writing the project, with the full history
Documents
The order and what both sides add to it in writing.
The orderscope, fee and scheduleA scope changeonly in writing, when one is neededThe code archivefrom the day of acceptance
Billing
An invoice at each payment stage, with its status.
Invoice: the advance1/3, before work startsInvoice: a stage1/3, after a stage is acceptedInvoice: the final part1/3, after final acceptance
Project channel
Discord or Slack, next to the panel.
A summary every weekwhat was done, what is next and which decisions are needed

Throughout the project

InformationThe test versionat a separate address, from the first daysThe link to the test version and how much of the project is paid.
ChatTalking to the developerthe person writing the project, with the full historyYou raise questions and notes right in the panel.
Project channelA summary every weekwhat was done, what is next and which decisions are neededDiscord or Slack, next to the panel.

Onboardingthe account and the project channel

DocumentsThe orderscope, fee and schedule
BillingInvoice: the advance1/3, before work starts

Prototypethe interface before code

BillingInvoice: a stage1/3, after a stage is accepted

The buildon the test version

DocumentsA scope changeonly in writing, when one is needed

Testingand final acceptance

DocumentsThe code archivefrom the day of acceptance
BillingInvoice: the final part1/3, after final acceptance

Releasewith the code handover

ReportsThe project handoverthe repository, documentation and access

Adding a feature midway is a scope change both sides confirm in writing, together with the new price and date (cl. 3.3).

How we work Payments and invoicing

What clients say

Reviews in full, translated from Polish, each beside the project it is about. Each mentions contact or support at every stage of the project.

Project: WaveHost
"Vulcode.com built our website and we are very happy with the result. The site runs smoothly, is well optimised and displays correctly on every device. The whole rollout went without a hitch, and the source code is clean and ready for further development. We appreciate the punctuality and the technical support at every stage."
Szymon
CEO, WaveHost
Trustpilot, 9 June 2026
Project: Sinlege
"Highly recommended. The site is fast, looks great on mobile, and turned out exactly as we agreed. Great communication at every stage and zero issues with revisions. We will definitely keep working together on future projects."
Krzysztof
Owner, Sinlege
Review on the VulCode site
Project: SafeBands
"Full professionalism and great communication. The system was delivered smoothly, reliably and in line with the spec. I appreciate the flexibility and technical support at every step. We will definitely continue the collaboration on the next stages."
Miłosz
Founder, Safebands
Trustpilot, 27 May 2026