Armature Studio / Interactive guide
A website. A connected system.
Select a part to see what it does, who controls it and how it connects to the rest. This is an illustration of project scope, not a live system status or an automatic quote.
01 / Core build
The place customers arrive.
Pages explain the business, show the work and give visitors a clear next step.
- Who controls it
- Your business owns its domain and the agreed deliverable.
- How it connects
- Content shapes the pages. Inquiries and optional booking connect visitors to the business.
02 / Agreed pages
The information people need.
Services, project work, images and copy are organized around the visitor’s questions.
- Who controls it
- Your team supplies and approves business facts, assets and permissions.
- How it connects
- The agreed content areas connect to the admin portal; initial copy and page limits belong in the scope.
03 / Core build
A request reaches a person.
A visitor sends the project details needed to start a useful conversation.
- Who controls it
- Your business controls the destination account and who follows up.
- How it connects
- Website → form provider → agreed inbox or system. The destination needs a real delivery check, not only a success message.
04 / Included / agreed controls
A place to manage the build.
The portal brings the content and controls agreed for the project into one place.
- Who controls it
- Your authorized team uses its own accounts; access and responsibilities are agreed.
- How it connects
- Admin controls connect to the delivered content or functions. Full handoff can include source, documentation and a walkthrough for managing changes with AI.
05 / Optional connection
An existing calendar, connected.
A straightforward link or embed lets visitors use a booking service you already have.
- Who controls it
- Your business owns the booking account and pays its service costs.
- How it connects
- The website connects to the existing service. Custom availability, scheduling or booking logic is separate software scope.
06 / Separately scoped
A tool for the work behind the site.
A CRM, client portal or operations tool can support a process an ordinary website does not handle.
- Who controls it
- Accounts, permissions, costs and the support arrangement are defined for that application.
- How it connects
- The app may connect the website to people, records and existing tools. Its first version, access and acceptance are quoted individually.
Start with the parts your business needs.
Agree the pages, connections and controls before the build. A custom app or a new integration gets its own scope.
Start a Project