Development: systems in Notion/BuildIn and custom platforms

Because the real volume is unknown until we review the spec: a price “by eye” has to include a margin for uncertainty and for rework. It’s more honest for me to name the hours after the strategy session, and better for you to pay for the actual work. Any hours left over carry on to the next improvements at the same rate.

A paid package is a guarantee for both sides. For me — time isn’t scattered across requests that lead nowhere; for you — you enter the work seriously: the hours are reserved for you, the task goes into the plan, and time is spent only on it. Every paid hour is visible in the time tracker.

I warn you in advance that the hours are running out — about 20% before the package ends. You can buy extra hours at the same price you paid for the package and finish the remaining tasks.

I work flexibly: extra hours are billed at the current package rate, or you can switch to a different package.

It depends on scope: how many databases and fields, who edits what and which way the data flows. For a “Notion → website” link — posts, materials, enquiries — the base 20-hour package is not enough: you’ll need more, a reasonable guide is 35 hours and up. If there are many scenarios — catalogue, filters, two-way sync — the scope grows further.

A website with an admin panel starts at the 35-hour package: page structure, layout, content management, forms and a technical SEO foundation. A platform with user accounts, roles, a database and integrations starts at 60 hours. I scope it after the strategy session; after that you pay for the actual hours tracked in the time tracker.

There is no separate monthly plan: support continues at the same rate and package we used for development — you simply renew the hours for the next period. Alternatively, you pay for hourly development: at 5–10 hours a month that is the current hourly package rate, and unused hours carry over to the next tasks. The work covers the technical side: updates, improvements, integrations, fixes and system consultations. Copy, photos, content filling and social media are not included — I’m a developer, not a content manager. For third-party code I work at 1.5× the rate: understanding someone else’s implementation and fixing it afterwards is extra effort.

Yes, always. After development I record video instructions for the system and hold a training call for you and the team. Further support — under a new hour package or at the standard rate.

Yes. I’m a registered self-employed professional — we’ll formalise our work with a contract, and you’ll get a receipt.

I don’t estimate before discovery: a fixed “eyeball” price includes a buffer for unknowns. After the strategy session I give the scope in hours: a small CRM in Notion/BuildIn is usually 40–80 hours, a custom platform — from 120.

A CRM covers clients and sales: leads, deals, reminders. An ERP covers the whole business: purchasing, inventory, finance, projects and employees. Teams usually start with a CRM and expand to an ERP once sales are under control.

AI agents take over the routine: qualifying leads, suggesting the next step, summarising conversations, drafting proposals and reminders. Decisions and money stay with people. These automations are built into the CRM or the platform.