CAPABILITIES
Features We Build Inside a Website
A website can hold work usually done by hand: taking bookings, sending invoices, limiting who sees which data. This page covers the features we build, the features we tell you not to build, and how additions are priced.
- Site
- Account
- Booking
- Payment
- Panel
Tell us the business and which page matters most.
Systems we build
Eight features come up most often. No project needs all of them.
Accounts & authentication
Visitors get their own identity, and pages adapt to it.
Details
- Sign up, sign in, sign out.
- Access differs by role.
- Sessions expire; access can be revoked.
Booking & scheduling
Bookings come from real availability.
Details
- The calendar shows open slots for each service and its length.
- Confirmation by email or WhatsApp.
- Reminders before the appointment; guests cancel themselves.
Payments
Payment status is readable without a bank statement.
Details
- One-time charges and recurring plans.
- Invoices generated, history kept per customer.
- Pending, paid and failed states in the panel.
Admin panel
Your team edits text, photos and prices without waiting for a developer.
Details
- Pages, services, schedules and staff records.
- Admin rights limited by role.
- A change log records who edited what.
Dashboard & reporting
Orders and signups sit on one screen.
Details
- Orders, signups, and the pages people leave most.
- A weekly summary by email.
- Data exports to a spreadsheet.
Integrations
The site connects to the tools your team already uses.
Details
- Payments, calendars, shipping and CRM through their APIs.
- Webhooks push data without anyone copying it.
- Automatic messages by email or WhatsApp.
Multiple languages & technical SEO
Each language has its own address, and pages are built for search engines.
Details
- Separate address per language.
- Titles, descriptions and structured data per page.
- Sitemap, redirects and index rules set during the build.
Security & performance
Data is checked on the server, and pages are tested on a mid-range phone and a slow connection.
Details
- Validation runs on the server before storage.
- Access rights are checked on every request.
- Images and scripts trimmed to keep pages light.
Not sure yet? Describe what the site has to do.
The three promises
Timing is stated before work starts
Every stage has an estimated duration in the quote. When a request adds time, we say what it costs before that part is built.
Features are written before the build
The feature document lists what gets built, how the site works, what waits, and why. Anything outside that document is treated as additional work, priced and agreed before it starts.
Bugs after launch are fixed without charge
A bug after launch is fixed at no extra cost. Monthly maintenance is available if you want it, quoted separately from the initial work.
If the schedule cannot take your date, we say so in the first reply.
The earliest start date is stated in the first reply.
How it works
Conversation
One call of 30 to 45 minutes: what the site is for, who uses it, which features you need.
Feature document
After the call we send a document: the features to be built, how the site works, what waits, and the estimated duration of each stage. The build follows it.
One contact through the build
One person holds the project from structure to build. Feedback goes to that person, nothing is forwarded.
Handover
You get the code repository, hosting and domain access, the feature document, and a short guide for editing text and photos. The site can be handed over entirely to your team or to anyone you appoint.
Fit or not
A fit if
- You are starting a new site, not asking us to take over one that already runs.
- You want the features written and approved first, then built to that document.
- Photos and copy exist, or you want us to shape them.
- You want hosting and maintenance available as a separate agreement.
- You want the site, the code and the access to be fully yours.
Not a fit if
- The site has to be live this week.
- You want us to take over and update a site someone else built.
- You want features added without adjusting the agreed cost.
- The budget in mind is a marketplace template price.
- Nobody answers the enquiries that come in.
One matching point is enough.
FAQ
What do I approve before work starts?
A feature document: the features to be built, how the site works, what waits, and the estimated duration of each stage. The build follows that document.
What if I want a feature added after the document is approved?
Anything outside the document is treated as additional work. We state the cost and the extra time first, then build it once you agree.
Can features be added at launch, as an update?
Yes. A launch update works the same way: a new feature goes in through your approval, with the cost stated before the work.
Do you offer hosting and maintenance?
Yes, quoted according to the agreement made at the start. There is no automatic plan: you approve the scope and the cost before the service runs.
Can you take over an existing site?
No. We build new sites from scratch and do not maintain or update sites built by someone else.
Who maintains it after launch, and can it move?
After handover the site, the code and the access are yours. It can move to another provider or team. Maintenance from us is optional, through an agreement.
Send a brief
- What the business does
- Which feature matters most to visitors
- A launch date, if you have one
The first reply arrives within two working days, with questions and a schedule estimate.
WORK WITH US
One project at a time. Tell us the business and the page that matters most. The first reply brings questions and a start window.
Or write tohello@foxible.com
