Working with Orwell Lab FAQs
How Orwell scopes and delivers websites, software, AI and automation, including discovery, project evidence, hosting, handover and support.
What does Orwell Lab build?
Orwell Lab builds business websites, custom software, AI agents and automation. Projects can stand alone or connect: a public website can feed a CRM, a customer portal can link to an operational system, and AI assistance can support a defined workflow. The starting point is the business outcome and the people using the system.
Link to this answer ↗Do I need a technical brief to speak to Orwell?
No. Describe your business, the people involved and what you want to build or improve. Examples of the current process are useful, including where staff repeat work or customers get stuck. A free 30-minute discovery call helps establish fit and a practical next step. A detailed technical specification can follow once the problem is understood.
Link to this answer ↗Can you handle website development and the backend together?
Yes. Orwell works across public websites and the software behind them. The Walthams project spans a website, staff workspace and landlord and tenant access foundations. The scope of a connected project should specify the customer journey, operational workflow, data ownership and integrations, with separate acceptance criteria for each part.
Link to this answer ↗Where can I see examples of Orwell’s work?
The work collection covers Walthams, Eastmans, Socialroom, Cranbrook Legal and Klientflo. Each project page explains the brief, delivered scope and relevant rollout conditions. Public websites and product demonstrations are linked where available. Some operational systems are private, so the pages describe the work without exposing customer records or inventing performance results.
Link to this answer ↗How is a project scoped before development?
We map the user journey, current systems, handoffs and constraints. The brief identifies deliverables, responsibilities, dependencies and how the result will be tested. For AI work, we also define permissions and review points. A clear first release makes progress easier to assess and gives both teams a basis for agreeing any later scope changes.
Link to this answer ↗Can Orwell work with our existing internal team?
Yes. Agree responsibilities for design, development, access, content, testing and operational support at the outset. Existing staff bring essential knowledge of the process and its exceptions. Regular reviews should use working examples so feedback is concrete. Documentation and handover then support the team that will operate or extend the system.
Link to this answer ↗Do you provide hosting and ongoing support?
Orwell can deliver to your infrastructure or provide hosting and support under an agreed managed arrangement. Specify monitoring, backups, maintenance, incident handling and improvement work in the scope. External AI, messaging and other service accounts may have separate usage costs. The right arrangement depends on your team’s capacity and how the system is used.
Link to this answer ↗What should we prepare for a discovery call?
Bring a short description of the business, the main problem or opportunity, examples of the current journey and any known deadline or budget constraints. Note the systems involved and who will use the result. You do not need to share confidential records at this stage. The purpose is to identify a sensible next step, not to arrive with every technical decision made.
Link to this answer ↗Apply it to your business.
Every project starts with its own context. Bring your questions to a free discovery call and we’ll help identify a sensible next step.
Talk to Orwell ↗