- Should the project use WordPress or a custom application?
- WordPress is a strong starting point for business websites, publishing, and WooCommerce stores where content management matters. A custom application fits a specific product, interface, or workflow that needs more than a website. An integration may be enough when the tools already exist. We compare these options against what you need to do before choosing the build.
- What should I include in a project inquiry?
- A short description of the goal, the website or process as it works today, and what you want to change is enough to begin. Add relevant links, known constraints, and a timeframe if you have one. A rough budget range is optional and can help shape the proposal.
- How are cost and timing decided?
- After the requirements and dependencies are clear, the proposal documents the deliverables, assumptions, cost, and delivery estimate. Content readiness, third-party systems, access, and feedback timing can affect delivery, so these are made visible before work starts.
- Can you improve an existing website or application?
- Yes. The work can start with a specific feature, template change, integration, or continued development. The inquiry should include the current URL or product context and the change you have in mind.
- Do projects need calls or meetings?
- No. Briefs, proposals, progress, previews, and feedback can all be handled online in writing, with replies by email.
- What happens at delivery?
- The proposal defines the handoff: the agreed build, relevant source or configuration, documentation, and any guidance for using or updating it. Hosting, third-party accounts, licences, maintenance, and future changes are clarified in scope so responsibility is clear. Continued development can be agreed as a separate next step.
