Your public front door
Services, products, proof, useful information, and a clear next step for the person visiting.
Websites & systems
Public presence at the front. Useful structure behind it.
A business should not have to force everything through a contact form, a spreadsheet, and someone’s memory. Tecknomancy builds the public-facing website and the operational tools behind it.
A plain answer
What is the difference?
A website is the public-facing part of your business. It explains what you do, demonstrates credibility, and gives people a clear route to contact, book, buy, or visit.
A web system handles work behind the scenes: bookings, customer accounts, staff actions, admin, approvals, records, reporting, and automation. It can stand alone or work with the website.
The engine behind the work
Operational logic for the people running the business and the customers using its services.
A complete service path
A customer finds you, understands the offer, books or signs in, and the business has the tools to handle what happens next.
Common builds
Where most projects fit.
We start from the actual business problem, then choose the lightest structure that can do the job well.
| What is happening now? | A practical next build | What it can include |
|---|---|---|
| “People cannot quickly see what we do.” | Business website | Clear service pages, examples, contact routes, local information, and conversion-focused structure. |
| “We manage appointments by message.” | Website with booking | Availability, booking requests, calendar logic, reminders, and a cleaner experience for clients. |
| “Our team repeats the same admin every day.” | Internal tool or automation | Forms, records, workflow steps, exports, notifications, and less manual repetition. |
| “Customers need their own secure area.” | Customer portal | Accounts, verification, protected information, requests, status updates, and self-service tools. |
| “We need one system to run the operation.” | Custom business system | Admin panels, customer records, bookings, approvals, reporting, and role-based access. |
How a system takes shape
The work is planned before it is decorated.
A system is not a pile of features. It is a sequence of people, decisions, information, and consequences that need to work reliably together.
Map the moving parts
Who uses it, what information arrives, what has to happen next, and which parts should stay private.
Build the critical route first
The core booking, approval, account, or admin job comes before optional decoration and future extras.
Leave room to grow
Useful systems change as the business changes. The structure is made so that growth has somewhere to go.
Less back-and-forth
Appointment requests, time slots, confirmation flows, event registration, and a clearer view of availability.
Protected access
Registration, verification, user areas, staff roles, customer records, and the tools to manage them.
Stop repeating yourself
Purpose-built utilities and automated steps that save time, reduce errors, and keep routine work moving.
Ownership & commerce
A system that belongs in the business.
When the work involves orders, payments, customer accounts, or staff operations, the boundaries are agreed before code is written.
Your business stays yours
Your customer data, content, operational records, and merchant relationships remain connected to your business. Tecknomancy retains reusable TecknoCore foundations, not your customer list.
Provider accounts in your name
For payment-enabled work, we scope a client-owned SumUp, Stripe, PayPal, Square, or other suitable provider account. Provider approval and the project requirements decide what is appropriate.
More than a checkout
Orders can connect to stock, fulfilment, booking, customer updates, refunds, admin control, and reporting. The precise route is designed around how the business actually works.
A direct studio
One builder, close to the detail.
Tecknomancy is run as a focused sole-trader studio. You work with the person who is listening to the operation, shaping the plan, writing the code, and responsible for the final working result.
The standard
Build the thing that earns its place.
Not a system for the sake of having a system. A useful part of the business that removes friction and gives the people using it a better route through the work.