Frequently asked questions
A few things worth knowing before we begin.
These answers explain our general approach. The details of your project belong in its written proposal.
What kinds of work do you take on?
Company websites, landing pages, WordPress and ecommerce work, custom web applications, dashboards, booking systems, API integrations, automation, UI/UX design, and scoped maintenance or performance improvements.
Can you work with an existing website or application?
Yes. We can review the current system and the changes you need. The proposed approach depends on its condition, available access, technology, and dependencies.
Should I choose WordPress or custom development?
That depends on your content, workflows, integrations, and management needs. We assess those requirements before recommending an approach.
How much will the project cost?
Cost depends on the agreed scope, complexity, dependencies, and deliverables. A written proposal sets out the price and payment terms for your consideration before work begins.
How long does a project take?
Timing depends on the scope, available content, feedback, and external dependencies. Estimates and milestones are discussed during scoping rather than promised before the requirements are understood.
Do I need a complete brief?
No. Start with what you want to achieve, who will use it, and what is not working today. Essential features, a budget range, and preferred timing help narrow the options.
Can you connect the tools we already use?
Potentially. We first check API availability, provider restrictions, required account permissions, and the data involved. The proposed integration depends on those findings.
Who supplies content and design assets?
Content, brand assets, images, and any requested content support are discussed during scoping. The proposal identifies what each side needs to provide and any related work included.
Are hosting and third-party subscriptions included?
They are not assumed to be included. The proposal distinguishes development work from hosting, domain names, licenses, subscriptions, and other provider charges.
Is ongoing support included?
Maintenance and support arrangements are defined for the specific engagement. Ongoing work is not automatic; included tasks and any response arrangements need to be agreed.
What happens if the requirements change?
We review the requested change and its effect on scope, price, and timing before agreeing how to proceed.
What will I receive at handover?
The proposal defines the deliverables, documentation, access arrangements, and any training or maintenance included. Ownership and licensing terms are also addressed in the project agreement.
Have a question about your project?
Include it with your inquiry so it can be considered alongside the requirements.