Voyagerroc Technologies

Four steps from the first message to acceptance.

At Voyagerroc Technologies a job moves in four steps: you describe it briefly, we talk and write the scope, we build and show interim deliveries, and we go through the acceptance checklist together. Each step ends with something in writing in your hands.

  1. You describe it briefly

    In a few sentences you write what you do, what you want to change and when you need it. You do not need technical terms; the words of your own work are enough.

    If the job is not a fit for us, we say so in our first reply.

    From you
    Three short answers
    From us
    A first reply and a proposed call
  2. We talk, then write the scope

    In a short call we make the job clear together. Then we share the scope sheet: what will be delivered, what stays outside, the acceptance criteria, who approves what and what happens if something goes wrong.

    Price and timing are quoted from that sheet. Work does not start before you approve the scope.

    From you
    A call and your approval
    From us
    The scope sheet and a quote
  3. We build and show

    The work moves in the order written in the scope. You see interim deliveries and send your comments in writing. If a new request falls outside the scope, we say so first and quote it separately.

    Where we use AI

    We use AI tools when writing code, drafting text and automating repeated work. We do not present that as proof of quality: everything delivered is checked against the acceptance criteria in the scope.

    In automation work, steps that decide on money, legal matters or customer data are tied to human approval.

    From you
    Collected, written feedback
    From us
    Interim deliveries
  4. We accept it together

    We go through the acceptance checklist together. If an item on the checklist does not work, how it is handled is stated in the written scope. Files, account access and handover notes pass to you.

    If something goes wrong afterwards, the route on the satisfaction and complaints page applies.

    From you
    Acceptance
    From us
    Handover: files, access, notes

Sample scope sheet

The fields of the scope sheet and why they are there

Every job uses the same fields; the content is written for that job. The notes below explain what the fields are for. They are not a published client scope.

The job
What will be done, in your own words.Why it is there: It shows that both sides understand the same job.
Deliverables
Everything you will receive, item by item: files, builds, accounts, access, notes.Why it is there: It answers “was that included?” before the work ends.
Out of scope
What is not part of this job is written down too.Why it is there: When a new request appears, both sides can see that it is a separate job.
Acceptance criteria
What we will look at together to call it done.Why it is there: Acceptance becomes a list you can check, not an impression.
If something goes wrong
How you tell us, and what happens next.Why it is there: The route to follow is known before anything goes wrong.
Approver
Who gives feedback on your side.Why it is there: Feedback comes from one place; the work does not wait between conflicting comments.
Ownership and handover
Who holds the code, files and accounts after delivery.Why it is there: What stays with you when the job ends is known from the start.

Price and timing are quoted from this sheet. Work does not start before you approve the scope. Responsible person: Erol Tasci.

Last updated: