Samples of our work: the documents you get when we work together.
Before you hand us a project, see what you'll have in your hands: the written proposal, the connection map, the tracking plan, the checklist before go-live, the handover note and the monthly report. They look exactly like the real ones, in English or Greek.
6DOCUMENTSYOU GET
WHEN YOU GET EACH ONE
Every project is different, but the documents come in the same order. You get the ones that fit yours.
The proposal
After you tell us what you need: what we'll set up, in which weeks, and for what fixed price.
The connection map
Before we write code for a connection: which system has the last word on each piece of data.
The tracking plan
Before we set up Google Ads tracking: what we measure, where it's sent and under which consent.
The go-live checklist
A few days before the new eshop or Odoo goes live: what we checked, what's left and who's doing it.
The handover note
On handover day: accounts, passwords, and where everything runs.
The monthly report
Every month, if we keep working together: one page on what happened and what changes next.
THE PROPOSAL
Once you tell us what you need, we send you a written proposal. It says what we'll set up, what isn't included, which weeks each part takes and what we need from you.
The price is fixed, one figure for the whole project, and it's written in the proposal. If something comes up along the way that we hadn't planned for, we write it up separately and you approve it before any work starts.
The amount is missing from the sample on purpose. We don't publish prices, because every project is different.
PROPOSAL
Company S.A. · new eshop with OdooPage 1 of 3
1What we'll set up
- A WooCommerce eshop with 1,800 products from Odoo
- A connection to Odoo for prices, stock and orders
- A cookie banner and sales tracking in GA4
- Training for two people from the office
2Not included
- Product photography
- Google Ads campaigns
3Timeline
4Price
Fixed price for the whole projectthe amount goes in your own proposal
Anything outside the proposal is written up separately, and you approve it before it's done.
Athens, 14 October 2026
THE CONNECTION MAP
When we connect two systems, for example your eshop and Odoo, we write the connection map with you before we write any code.
It says which system has the last word on prices, stock and customers, what happens when the connection drops, who sees the errors, and who owns the code and the passwords. Whoever maintains the connection later knows exactly how it works, and your group's IT can read it too.
How we build such a connection is on our eshop–ERP integration page.
CONNECTION MAP
Company S.A. · eshop and OdooPage 3 of 8
1When the two systems disagree
| Data | Wins | Then |
|---|---|---|
| A price changed in both | Odoo | Email to the pricing manager |
| Stock | Odoo | The eshop is corrected within 5 minutes |
| Customer address | The eshop | Goes to Odoo with a note |
2If the connection drops
The order waits its turn and is resent after 1 and 5 minutes. Its order number stops it going in twice.
3Who sees the errors
The warehouse manager, by email and as a task in Odoo. If it isn't fixed within two hours, Premiumspace is alerted too.
4What belongs to you
The code, in your own account. The passwords, in your own Odoo. The record of every transfer (logs), for 12 months.
Agreed on 14 October 2026
THE TRACKING PLAN
Before we set up tracking for Google Ads and GA4, we write down with you what we measure. For each event, the plan says where it's sent, when it counts, with what value, and what happens when a visitor declines cookies.
It's the document anyone working on your tracking later will read. Thanks to it, a purchase counts once rather than three times, and nobody mistakes an add-to-cart for a sale.
How we set it up is on our Google Ads page.
TRACKING PLAN
Company S.A. · eshop, GA4 and Google AdsVersion 2 · 21 October 2026
1What we measure
| Event | Sent to | When it counts |
|---|---|---|
| Purchase | GA4 and Google Ads | When the order is paid, once per order number |
| Wholesale enquiry | GA4 and Google Ads | When the form is sent |
| Phone sale | Google Ads, from Odoo | When it closes in Odoo, with the click ID |
| Add to cart | GA4 only | Measured, but not a conversion |
2Purchase value
Excluding VAT and shipping, as recorded in Odoo.
3Consent
No tag before “Accept” on the banner. With “Reject”, the sale counts only in Odoo.
4Changes
Every change is written here first, with a date, and only then made in the tags.
THE GO-LIVE CHECKLIST
A few days before the new eshop or the new Odoo goes live, we go through a checklist with you. For each point it says whether it has been checked and who is taking care of it.
Anything still open is written down, with a name and a date, so nothing turns up afterwards. On go-live day we're with you, checking the first orders in Odoo one by one.
GO-LIVE CHECKLIST
Company S.A. · go-live 3 November 2026Page 1 of 2
1Eshop
- Checked: Test orders by card, cash on delivery and bank transferPremiumspace
- Checked: Old URLs lead to the new pagesPremiumspace
- Still open: Final photos for 12 productsYou, by 31 Oct
2Odoo and the connection
- Checked: Same stock in the eshop and Odoo, for 50 random productsPremiumspace
- Checked: An order goes through once, even with the connection downPremiumspace
- Checked: An invoice with its MARK number from a test orderTogether
- Still open: The accountant knows about the new invoice seriesYou, by 31 Oct
3Tracking
- Checked: Purchase with “Accept”: counted oncePremiumspace
- Checked: Purchase with “Reject”: no tagsPremiumspace
Checked on 29 October 2026
THE HANDOVER NOTE
When a project ends, we hand you a note listing every account, where everything runs and who has access.
The accounts are opened in your company's name and the passwords stay with you. We have access while we work together, and you can remove it whenever you like.
The code lives in your own account, and the note explains how someone else picks it up. If you continue with another team tomorrow, they don't start from scratch.
HANDOVER NOTE
Company S.A. · eshop and OdooPage 1 of 2
1Accounts
| Account | Owner | Our access |
|---|---|---|
| Domain example.com | You | None |
| Eshop hosting | You | Admin, while support lasts |
| Odoo | You | A user in our own name |
| Google Ads and GA4 | You | Access you can remove |
| Code repository | You | Permission to make changes |
2Passwords
In the company's password manager. Never sent by email.
3What runs where
The eshop and the connection on your own hosting. Backups every night, kept for 30 days.
4If someone else takes over
The connection map, the tracking plan and the setup instructions are in the repository, next to the code.
Handed over on 12 November 2026
THE MONTHLY REPORT
If we keep working together after handover, every month we send you one page: how much went through the connection, which errors happened and how they were fixed, what we changed and what we're doing next month.
The figures come from your own systems, Odoo and the eshop, not from estimates. If we also run your Google Ads campaigns, the same page shows how many orders each one brought in.
MONTHLY REPORT
Company S.A. · October 2026One page
- 1,284
- orders from the eshop to Odoo
- 1,279
- invoices with a MARK; 5 cancelled before invoicing
- 3
- errors, all fixed
Orders per week
What happened
- The connection to the e-invoicing provider dropped twice. The invoices waited and were resent by themselves.
- A product without an EAN was held back from the feed. Fixed in Odoo the same day.
- Store pickup was added as a delivery option.
Next month
- Black Friday prices from Odoo, with the 30-day previous price
- WooCommerce updates, tested on a copy first
TRUE FOR ALL OF THEM
Written before the work
The proposal, the connection map and the tracking plan are written before we start, and you approve them. The work is built on them.
Yours to keep
The documents are yours, like the accounts and the code. You keep them, whoever carries on the work.
In English or Greek
We write them in the language your team works in, so your Greek accountant and your group's IT can both read them.
QUESTIONS
Are these real client documents?
No. They're made for this page, in the same form as the real ones. We never publish client documents, just as we never publish client names.
Why doesn't the proposal show an amount?
Because every project is different, and an amount without your project would only mislead. In your own proposal the price is fixed and written down from the start, and anything outside it needs your approval before it's done.
Do I get all six in every project?
The ones that fit your project. You always get a proposal and a handover note. A connection map when we connect systems, a tracking plan when we set up tracking, a go-live checklist when a new eshop or Odoo goes live, and a monthly report if we keep working together after handover.
What if I want to continue with another team?
You take the handover note, the code and all the documents. The accounts are already yours, so the new team knows from day one where everything runs and why it was built that way.
SEE THEM IN PRACTICE
Eshop–ERP integration
The connection map, and an order's journey from the eshop to Odoo.
Google Ads & sales tracking
The tracking plan, the monthly page and a sale step by step.
Odoo Greece
How we set up Odoo, with myDATA, delivery notes, ERGANI and payroll.
About
Who we are, how we work and what we build for you.
WANT A PROPOSAL OF YOUR OWN?
Tell us what you need, and we'll send you a written proposal like this one, with your project and your price.