VulCode

Who you work with at VulCode: the specialist who runs your project

You talk about your project directly with the person who runs it and writes the code, with no needless go-betweens. A team of professionals stands behind them, and the decisions and acceptance stay with you.

Working with us
Sample client panel screen: a project chat where the client accepts a corrected logo variant and the VulCode developer records the acceptance and gives the date of the test version

Who handles what

A typical project from the first message to care after launch. One specialist who knows every agreement runs it, so nothing gets lost between people, and the decisions and acceptance are yours.

You
  • First talk and quoteProject description and questions
  • Wireframes and prototypeFeedback on the prototype and approval
  • The buildDecisions and stage acceptance
  • Handover and careFinal acceptance
VulCode
the specialist who runs your project
  • First talk and quoteA quote with scope and stages
  • Wireframes and prototypeWireframes and a clickable prototype
  • The buildCode and the test version
  • Handover and careRelease, docs and warranty
  1. Straight to the lead

    You VulCode. Your message goes to the person who will run the project, and within an hour you get questions or a quote with the scope and stages.

  2. A prototype to approve

    VulCode You. Before any code is written, you click through a prototype of the key screens and send your feedback straight to the lead.

  3. Test version and summaries

    VulCode You. You check progress yourself on the test version, and every week you get a summary: what was done, what is next and what we need from you.

  4. Acceptance and handover

    You VulCode. After your acceptance the project goes live, and the repository, documentation and access pass to your company.

A specialist runs your project, not a go-between

You talk to the person who knows every decision in the project and writes the code, not to someone who passes messages on. A team of professionals stands behind them.

This is Michał Fox, founder of VulCode. I promise you four things.

I run projects from the first conversation: I quote them, plan the architecture, write the code and answer for the release. I do not pass you on to someone else, and whatever we agree goes into the project channel in writing.

A reply within an hour

You get a reply to your message within an hour: questions or straight away a quote with the scope and the stages. The quote is free and commits you to nothing.

No needless go-betweens

You talk about the project with me, the person who runs it, in the project channel, on video or in person. There is no broken telephone between you and the code.

Code you own

After acceptance and full payment the code rights pass to your company, together with the repository, documentation and access (cl. 6.1 of our terms).

A 90-day warranty

We fix bugs in our work at no extra cost, as standard for 90 days after final acceptance. The period goes into the order, and you report a bug in the client panel.

Michał Fox
founder of VulCodedualfroz.com

Where we talk and on what terms

The project runs in the project channel and the client panel, and for decisions we meet on video or in person. The contact rules are the same in every project.

Sample client panel screen: a project chat with the client's acceptance recorded by the VulCode developer
  1. You talk to the leadIn the project chat, on Discord or on Slack you write directly to the person who runs the project, in Polish or English. Every week you get a summary there: what was done, what is next and what we need from you.
  2. Decisions in writingWhen something needs a decision, we set up a short video call or meet in person, and write the agreement down in the project channel. A scope change needs both sides' written consent (cl. 3.3 of our terms).
  3. Files in the client panelThe schedule, files, invoices and requests are in the client panel, visible to both sides from the first day. You check progress yourself, on a test version from the first days.

How the handover works

The handover is run by the same person you have talked to since the first message. At the end you get everything needed for anyone to develop the project further.

Confirmed acceptance

Final acceptance

You check the project on the test version against the scope in the order.

A working project
Confirmed acceptance

Release

The project goes live on a date we agree together, with monitoring.

The repository with you
A working project
Confirmed acceptance

Code and documentation

The repository with its history, and the setup, architecture and deploy docs. We walk your team through the project on a call.

Code rights and access
The repository with you
A working project
Confirmed acceptance

Access and rights

Accounts in your company's name and, once the full fee is paid, the rights to the code (cl. 6.1 of our terms).

Requests in the client panel
Code rights and access
The repository with you
A working project
Confirmed acceptance

Care after launch

The warranty per the order, as standard 90 days from final acceptance, and after it maintenance under a separate agreement, if you need it.

Common questions about the team and contact

Answers about who runs the project, contact and meetings.

Talk to the person who will build your project

Tell us what you need. We will reply within an hour, with questions or straight away with a quote.