Website creation
AI-assisted creation with a defined brief, human review and a clear handover.
AI automation & SaaS
We are developing a website-first software business for organizations that need a clearer digital presence and more efficient workflows. Application creation, analytics and business automation extend that direction.
The direction we are developing
Workflow automation
Connect recurring tasks, information and approvals around the way a business actually works.
Applications & analytics
Explore focused applications, dashboards and reporting around a specific operational need.
Reusable products and scoped delivery
SaaS products
A repeatable product designed around a common customer need, with a defined feature set and support model.
Custom implementation
A bounded engagement for a business-specific workflow, integration or handover. Its scope and delivery responsibilities must be agreed separately.
Website-first development
Start with the website creation journey; extend to broader automation where customer evidence supports it.
Who we want to hear from
Business owners, operations teams and organizations exploring a website or a bounded software workflow.
Bring a process worth improving: what happens today, who uses it and what a useful result would look like. We can use that brief to explore fit, scope and the first test.
Discuss this businessFrom a brief to a first test
Understand
Define the user, current process and desired result.
Agree the scope
Clarify deliverables, review, ownership and practical constraints.
Test and learn
Assess a bounded first approach before committing to wider delivery.
A conversation, not a product checkout.
This business is in development. Product availability, commercial terms and delivery commitments will be confirmed for a specific engagement.
AI website creation: what the brief should cover
A useful website brief describes the customer, the offer and the action visitors should take. It also identifies languages, page types, brand assets, required integrations and who approves the content. An AI-assisted draft still needs human review of claims, navigation, accessibility and the enquiry journey. Publishing and ongoing support must be included in the agreed scope rather than assumed.
Business automation and dashboards
Start with one recurring workflow: where information comes from, who uses it, which decisions need approval and what happens when a step fails. A dashboard should answer a specific operational question, with understood data sources and permissions. These are potential implementation journeys for discussion, not a claim that a ready-made connector library or live SaaS platform already exists.
An illustrative first engagement
One possible starting point is a company website with a defined page set and a clear enquiry path. Another is a single workflow that turns an approved source into a reviewed report. Before either proceeds, the parties would agree the deliverable, responsibilities, acceptance checks, ownership, pricing and support. These examples are proposed scopes, not completed customer projects.
From an AI-generated page to a useful business website
Generating a page is only one part of website creation. A business website needs clear customer information, a responsive layout, accessible forms and maintainable content. Before launch, define the language versions, search metadata, deployment, account ownership and acceptance checks. The proposed AI-assisted workflow should make these responsibilities easier to review; the first generated screen is not a finished product.
Explore related information
Questions about this direction
What is the first product focus?
Website creation is the first focus. Applications, analytics and broader workflow automation are extensions to evaluate against customer needs.
Is this SaaS or a custom service?
Both models are being evaluated separately. SaaS means a repeatable product; custom implementation means an agreed workflow, scope and handover for one business.