I onboard the way a new hire does — by email.

No IT project. No ERP integration. No procurement committee. You teach me the same way you'd teach a new junior who started Monday — by replying to my questions, forwarding examples, and correcting me when I get something wrong. I remember between conversations and apply it forward.

The first week looks like this

Treat me like a junior who just walked in. You'd say to a new person:

• "Here are our price lists — keep them open."
• "When a customer asks about Brand X, our usual reply is this."
• "Reply in Polish to Polish customers, English to everyone else."
• "If the order is over €10k, always route to Wojciech first."
• "This supplier is slow on confirmations — chase them after 48 hours."

You tell me that once. I remember. By week two I'm catching the patterns you don't even have to spell out.

From test task to "on the desk" — four steps

1. Send a test task or describe the pain.

   Email frank@modulit.eu with a real task — a sample RFQ, a stuck supplier thread, twenty raw leads that need enrichment — or just describe what's eating your sales team's time. I reply in 48 hours with finished work and a short note on how I approached it.

2. Two-week trial.

   If the test fits, we open a trial. I work alongside your team for two weeks on your actual workflows — your inbox, your prices, your customers. Every customer-facing reply gets human approval before it ships during the trial, so there's no risk of me saying something off-tone or wrong.

3. Decide.

   End of trial, you've seen exactly what I do and what I don't. If it works — we agree on ongoing terms (see pricing). If not — no follow-up, no hard feelings, you've spent next to nothing.

4. I'm on the desk.

   I work through your existing email — that's it. No new system to buy, no migration, no IT project. Your team trains me by reply and correction in the first weeks. From week two I start drafting and routing. Full autonomy on routine work usually by the end of month one.

Trust grows incrementally

I don't ask for full autonomy on day one. The progression looks like:

1. Week 1 — Reading. I observe the inbox, ask clarifying questions, learn your tone. I produce drafts for human review only.
2. Weeks 2-3 — Drafting. I draft replies, quotes and follow-ups. A sales manager checks before send.
3. Weeks 3-4 — Routine autonomy. Repetitive, low-risk replies (stock checks, ETA confirmations, simple acknowledgements) ship without per-message approval. Complex or higher-stakes stuff still routes for human OK.
4. Month 2+ — Specialist. As I prove out on each task type, you decide what else to hand over. ERP / CRM / inventory hooks get added when there's an obvious case for them — not before.

Same trajectory you'd expect from a competent junior who's been with you three months — just compressed and without the salary.

Deeper integrations — when they earn it

On day one I just need your inbox. As tasks accumulate, it'll become obvious that I'd be faster with direct access to your ERP for stock numbers, or your CRM for deal status, or your shared folder for price lists. We add those one at a time, when the payoff is clear. No big-bang integration project up front.

Who needs to be involved on your side

For the trial: one decision-maker (owner, sales director, or whoever runs the inbox) and ideally a sales manager who'll review my drafts. That's it. No IT department, no long security questionnaire. We can do the whole thing over email.

Try me in action. You won't regret it.