Dealokr logoDealokr
Message templatesIntroducing Dealokr

Introduce Dealokr to your client, with a message for each step.

Explain the workflow simply, then identify the next action. Copy and adapt six messages to introduce Dealokr, prepare a review and accompany the final-file handoff.

Choose my message

A link sent without context leaves your client with questions: why this tool, what should they look at and what happens next? Your message can answer those points in a few lines, with a recognisable project and a specific action to take.

These templates accompany the project’s steps. To understand how the agreement, initial payment, preview and handoff fit together, explore how Dealokr works.

Choose the situation, copy the text and replace the fields in brackets. The message introduces the workflow you propose; its terms and available actions stay in the project. Check both before sending so you announce the right next step.

A professional prepares notes beside a laptop.
Check three reference points before sending.
  • The client recognises the project and understands why they received this message.
  • The terms you announce match the agreement and the actual project status.
  • The next action is specific: review terms, sign, pay, examine work or retrieve files.
01 · The first invitation

Introduce the workflow to a new client.

Your first message explains the workflow before asking the client to act. Name the project, describe what they will find in Dealokr and show where to start. You can introduce the tool as a clear way to organise the engagement, with an agreement to review, upfront payment made explicit and deliverables you will be able to examine together.

A professional works on a laptop in an outdoor space.
New client — introducing the project

Subject: Our [project name] engagement — agreement and next steps

Hello [Name],

For [project name], I suggest we use Dealokr to follow our agreement and the project steps. You will find the scope, price, deliverables and review conditions together.

Here is the project link: [project link]. You can verify your access by email, review the terms and sign. For this fixed-price project, 100% payment through Stripe Connect is planned before production starts.

I will then share a preview for your review before handing over final files under the project’s conditions. To begin, could you check that the agreement reflects our conversation?

Thank you,
[Signature]

Connect the message to what you have discussed

Send this text once the client understands the need and proposed scope. Replace the project name and check the terms before sharing the invitation. If full upfront payment is being introduced for the first time, give the client space to confirm it; the message should not present a new condition as something already accepted.

The first objective is to have the client review the agreement. They can find the amounts, deliverables and review process in Dealokr, then ask questions using a shared reference. Keep the message readable by leaving project-specific detail in that space, while making important conditions visible.

02 · An established relationship

Explain the change to a repeat client.

With a repeat client, start from your collaboration and explain what you propose for future projects. The new link gives you one place to find the terms, steps and responses. Introduce that approach before asking them to use it, while discussing the price, payment and handoff conditions you will agree for the next piece of work together.

Two professionals talk around a laptop on a terrace.
Repeat client — preparing the next project

Hello [Name],

For our next [project name] engagement, I suggest using Dealokr to bring the agreement, payment status, previews and your feedback together in one project.

We can review the scope, deliverables and review conditions before confirming the start. I will then send an invitation to [agreed email address] so you can access the project and take the planned steps.

Before that, let’s confirm [point to clarify: timing, scope or payment terms]. I can then prepare the agreement on the same basis as our conversation.

Best,
[Signature]

Introduce the arrangement, then confirm the terms

A client familiar with your methods needs to understand what changes in practice. You can explain that versions and responses will be connected to the engagement, then say when the invitation will arrive. The benefit is visible: they know where to find the agreement and the next action.

If payment, the start date or included revisions change, discuss those points separately and have them confirmed in the new project’s terms. Introducing Dealokr as a practical continuation should not make those decisions look like minor technical details.

Check the right contact

Confirm the email address of the person who will access the project and gather the information needed for the agreement. If a team takes part in the review, also agree who will consolidate its feedback. Dealokr provides the project workflow; your working arrangement determines who prepares the response.

03 · A question about the process

Explain Dealokr’s purpose and fixed-price payment.

When a client asks why you use Dealokr, answer with the concrete project sequence. They can read the agreement, understand the payment, examine the work and find the handoff. Make upfront funding of the fixed-price engagement and Stripe Connect’s role clear, connecting each step to the terms you have agreed for this particular piece of work together.

Two people review documents beside a laptop and a notebook.
Why Dealokr — a practical explanation

Hello [Name],

I use Dealokr so we can find the agreement and steps for [project name] in one place. You can review the deliverables, amount and review conditions before signing.

For this fixed-price engagement, you pay 100% of the agreed amount upfront through Stripe Connect, before production. I then share a preview for your feedback. Hosted final files are handed over after confirmation of the transfer, requested under the project’s conditions.

That gives us a shared reference for the agreement, version examined and following actions. Please let me know which point you would like explained before continuing.

[Signature]

Give the level of explanation the client needs

Start with the question your client is asking. If they want to know where to read the deliverables, point to the agreement. If they are asking about payment, confirm the total, planned timing and following step. A specific response helps more than listing every product feature.

To describe the funds precisely, the initial payment is collected in the platform’s Stripe balance before transfer to the freelancer’s connected account. The payout to the freelancer’s bank account is a separate step. Milestones within a fixed-price project funded upfront do not mean additional client charges at every review.

Stay faithful to the project’s conditions

Avoid adding a refund guarantee or a promise about how a disagreement will end. Explain the review and revision options actually included, then leave room for questions. Your message should support an informed commitment with an identifiable next action.

04 · Work ready to examine

Invite the client to review an identified preview.

When a preview is ready, the client needs to understand what they are examining and which response you expect. Name the version, agreed criteria and review point in the project. With a specific request, Dealokr connects the response to the work presented, while your message helps the client prepare useful, consolidated feedback on the material you have shared.

Colleagues discuss a project around a work table.
Preview available — requesting a review

Subject: [Project name] — preview [version] ready to review

Hello [Name],

Preview [version] of [deliverable] is available in our Dealokr project: [project link]. It lets you check [agreed criteria or points to examine].

You can examine this version, then approve the preview or request the included revisions through the project. For feedback, identify the passage or element concerned, what you observe and the expected result. If several people are reviewing, please consolidate their comments before responding.

The agreed review point is [previously agreed date or step]. This preview is for examining the work; the final package will be handed over through the planned next steps.

Thank you,
[Signature]

Help everyone decide on the same version

Before sending, open the right project and check that the announced preview is available. Name the version using a reference the client can find. For a page or prototype, specify the flow to check; for creative work, recall the brief’s criteria and the relevant formats.

You might request feedback on a screen’s readability, a message’s consistency or compliance with a specified format. The client then knows what to assess. A new idea that changes the scope deserves an explicit conversation before being included in production.

Announce a review date you have actually agreed

Complete the date field only if you have agreed that reference point. Keep the message’s dates and review conditions consistent with the project’s terms. The preview decision, transfer request and final access remain separate steps; a lack of response does not execute them automatically.

05 · Files ready to receive

Accompany the final handoff with useful references.

Your handoff message must match what the client can actually access. Check transfer confirmation and hosted final files before announcing their availability. You can then name the accepted version, package contents and external permissions to check, so the client knows what to retrieve and how to continue using the material included in the agreement for this project.

Colleagues consult a laptop and documents during a discussion.
After transfer confirmation — announcing the available package

Subject: [Project name] — final files available

Hello [Name],

The project transfer is confirmed and hosted final files are accessible in Dealokr: [project link]. The package corresponds to [accepted version] and includes [agreed files and formats].

You will also find [documentation or instructions actually provided]. For external elements [code repository, Figma, CMS or other], the planned access is [verified access and suitable handover method].

Could you check that you can find the listed files and let me know if your team is missing any information needed to use them?

Thank you for working with me,
[Signature]

Match the announcement to the project status

Use this template after checking the confirmation and availability you announce. If you are still preparing the files, describe what remains to be done instead of using a sentence that presents them as accessible. Client approval and a pending transfer request are not transfer confirmation.

The package may contain exports, source files when included and documentation. Follow the agreed list, using names the client recognises. Identifying formats and the final version helps them take over the work more than writing “everything is in the folder”.

Handle external access in the right place

Permissions for a code repository, Figma account or CMS are checked within that service. Adding a link to Dealokr does not change its owner or transfer its rights. Say what has actually been shared, then use a suitable channel for sensitive information.

06 · Your context and voice

Adapt the text to the channel and next action.

A template becomes useful when it uses the project’s language and the level of detail your client expects. Keep the information that enables action, then adapt the length to the channel. The Dealokr project carries the terms and steps; your email or short message helps the client find the right material at the moment it is needed.

A professional talks on the phone beside a laptop.
Short version — accompanying a first link

Hello [Name], here is the Dealokr invitation for [project name]: [project link]. After verifying your access by email, you can review the proposed agreement. For this fixed-price project, 100% payment is planned before production. Could you check the deliverables and flag anything to clarify before signing?

Choose the information that serves the action

In an email, a precise subject and a few paragraphs separate the context, link and expected response. In a messaging app, keep the invitation short when you have already discussed the scope. You can announce a review or handoff using the same principle, naming its actual status.

SituationKeep in the messageCheck in the project
First invitationProject, reason for the link and terms to review.Scope, amount and announced payment.
Review requestVersion, criteria and expected response.Available preview and review conditions.
Final handoffPackage, version and useful instructions.Confirmed transfer and accessible files.

Read the message as its recipient

Replace every bracketed field, remove unused options and keep your usual level of formality. Check the link, name, dates and deliverable references. The buttons only copy the template’s text: you review it and send it yourself through your usual channel.

Finally, ask a simple question: will the client know which action to take after reading? If several decisions are mixed together, choose the one that lets the project advance now. Dealokr keeps the shared agreement; your message gives human context to the step you are ready to take together.

Choose the template that matches the actual situation, complete its fields and check the action you announce. Your client should understand the workflow, find the right project and know where to begin.

Back to the messages
Sources and verification
  • Dealokr — Client invitations and email verification
  • Dealokr — Agreement and initial fixed-price payment
  • Dealokr — Preview review and revision requests
  • Dealokr — Transfer confirmation and hosted final-file handoff
  • Dealokr — Templates copied in the browser

Adapt these templates to the actual agreement and project status. Full upfront payment describes the fixed-price workflow. Approval, the transfer request and confirmation are separate steps; hosted files and external services have different access permissions.