Use cases
Each Project enables the operations that fit the business. The frontend stays yours.
Five starting points
Keep the frontend flexible. Run Products, Posts, Services and enquiries in the Project.
You want full control over how the store looks, and you refuse to rebuild catalogue, inventory and order management.
Design browse, cart and checkout around the brand while the team runs products, customers, orders, shipping and discounts in Webtools.
The website gets visitors, then everything after “I’m interested” falls apart.
Explain the offer, prove it with Past Works, capture a structured enquiry and keep each Opportunity moving in CRM.
Publishing often must not mean shipping code often.
Give editors a structured publishing workflow while developers keep full control of the reading frontend.
A church website changes every week. Calling a developer for every article, announcement or contact path does not scale.
Keep articles, media, programmes represented as Services where appropriate, subscribers and contact enquiries current from one Project.
A portfolio has to prove the work and help win the next project.
Turn Past Works into case studies, connect them to Services and follow every promising enquiry through the CRM pipeline.
Start with one project
Enable the capabilities this Project needs, then connect the frontend through the Storefront API.