Jon Doe3 weeks ago
"Really thorough and thoughtful, made sure we had everything we needed."
via Senja
For Irish SMBs
Integrations
The revenue-driving features local businesses ask for most — each one solving a real problem, built once in the component library and deployed consistently across every client site.
EUR & Irish VAT
GDPR-aware
No client backend
Static-first
Built with
Enquiry form
Leads straight to your inbox. No DM roulette.
CRM
Every enquiry becomes a contact with a follow-up action.
Scheduling
Bookings without a phone call.
Payments
Deposits & sales without a full checkout build.
Point of sale
Connect Square or SumUp to the site.
Reviews
Google reviews on the site — no widget, no cookies.
01 · Enquiry form
Phase 1"Customers message us on Instagram. Half never hear back and the others we lose track of. We have no way to capture leads properly."
Form submissions land instantly in your inbox. No backend to run, no new login to manage. Honeypot spam protection and GDPR consent recorded with every submission.
Message sent
Thanks — we'll be in touch within one business day.
Live form — submissions go to the Basin dashboard and arrive by email. Full implementation detail →
02 · CRM
Phase 2"Enquiries land in the inbox but there's no system. Follow-ups get forgotten, leads go cold, and I've no idea what stage anyone is at."
An Irish company, built in Galway. Action-focused CRM — every contact has one next action, so nothing falls through the cracks. A Netlify Function bridges the form and the API: no credentials in the browser.
Form submission
Netlify Function
OnePageCRM API
Contact + action created
Contact created in OnePageCRM
Name
Aoife Murphy
Email
aoife@example.ie
Source
Website enquiry
Note
"Tell us what you're looking for…"
Follow up · due tomorrow
How it works
The enquiry form posts to a Netlify Function instead of directly to Basin. The function validates the submission, forwards the email via Basin, and calls POST /api/v3/contacts.json on OnePageCRM to create the contact with a "Follow up" action set for the next business day. The API key lives in a Netlify environment variable — never in the browser.
Requires a OnePageCRM account. onepagecrm.com →
03 · Scheduling
Phase 2"We take all our bookings by phone and DM. We miss calls constantly and can't take anything outside business hours."
Acuity · Calendly · Cal.com — embed the client's existing scheduler behind a consent gate. Loads only after the visitor opts in, so no cookies fire on page load.
04 · Payments
Phase 1"Clients book and then ghost. I've no way to take a deposit upfront to hold the appointment — I just lose the slot."
Stripe Payment Links — card data never touches the site. Stripe hosts the payment page so PCI scope stays minimal. EUR shown inclusive of VAT.
Appointment deposit — holds your slot. Deducted from the balance on the day.
€25.00 incl. VAT
Pay deposit
Visa · Mastercard · Apple Pay · Google Pay — hosted by Stripe
05 · Point of sale
Phase 3"People ask if they can pay online or order ahead. My till is SumUp — I don't want to run a second system just to have a website shop."
Square · SumUp — deep links to the client's existing till. One inventory, one set of payouts, zero reconciliation overhead.
Order ahead or pay a balance — straight to the provider. No card data on the site, no new system to run.
Provider-hosted checkout — Visa · Mastercard · Apple Pay
06 · Reviews
Phase 2"We have 200 five-star reviews on Google but none of that shows on our website. New customers can't see them unless they go looking."
Senja — we connect to the API at build time and bake reviews into the page as static HTML. No widget script, no cookies, no consent gate needed. Google reviews import supported.
The review above is live data fetched from the Senja API and rendered at build time. Full implementation detail →
GDPR & consent
Consent before third-party scripts
Scheduling, maps and analytics set cookies — under GDPR/ePrivacy (Irish DPC) nothing third-party loads until the visitor opts in. A lightweight consent banner gates them. Forms carry explicit opt-in checkboxes. Payments and static reviews need no consent gate at all.