Working together

Clear expectations.
Better projects.

Understand the process, how a scope takes shape, and the questions worth asking before development begins.

01

Conversation

Describe the problem, existing workflow, users, and constraints. Decide whether there is a useful fit.

02

Written scope

Agree on deliverables, milestones, dependencies, cost, and terms before committing to work.

03

Build & handover

Review the work at agreed points and clarify deployment, ownership, and ongoing responsibilities.

Common questions

What to know before we start.

What happens after I get in touch?

Jon reviews your message and follows up to clarify the problem, scope, and fit. A conversation does not commit you to a project.

How much will my project cost?

Pricing follows discovery and an agreed scope. The proposal should identify deliverables, milestones, payment terms, and any third-party costs. The website calculator is an assumptions-based planning tool, not a quote.

How long does a project take?

Timing depends on scope, integrations, access, and feedback. A delivery plan is agreed for the work being proposed rather than promised before discovery.

Can we start with one small improvement?

Yes. A focused first milestone can test whether a workflow or integration is useful before expanding the project.

Can you work with my current hosting?

Existing hosting is reviewed for compatibility. Ciphrus works with PHP/MySQL, Python, JavaScript, and integrations; the proposed solution determines the hosting requirements.

How is AI used?

AI is considered where it helps with tasks such as text processing or drafts. Data handling, vendor dependencies, and human review points should be agreed before an AI integration is used.

What happens after launch?

Handover and maintenance responsibilities should be part of the agreement. Application care can be discussed separately; ongoing support is not automatically included.

Can I share passwords in the contact form?

Please do not. If access is needed, agree on an appropriate secure channel and the minimum permissions required.

Can we work remotely?

A remote engagement can be discussed during discovery. Agree how meetings, access, demonstrations, and handover will work before development begins.

A useful next step

Start with the problem.

Build a short project brief, then decide whether to share it with Jon.

Plan your project