How I Work
A clear process from the first discussion to delivery and ongoing support.
Every project is different, but the way I work stays consistent. I use one practical four-stage process to keep requirements, scope, responsibilities and next steps clear from the beginning.
The JENOBIX process
Four stages used across every service.
The details vary by project, but the working structure stays the same: understand the requirement, define the scope, carry out and review the work, then complete delivery and provide support where needed.
Consultation
I review your business goals, current challenges, target audience and technical requirements to establish a clear starting point.
Proposal & scope
You receive a clear proposal outlining the agreed scope, deliverables, priorities, timeline and investment before work begins.
Development & review
I carry out the agreed work with attention to usability, technical quality, maintainability and the actual business requirement.
Launch & ongoing support
After approval, I manage the launch or handover and can continue with maintenance, improvements and technical support as needed.
One point of contact
Flexible to the service
No unnecessary stages
The process stays structured without turning every project into a long agency-style workflow.
How each stage works
A structured approach that keeps requirements, decisions and delivery aligned.
The exact checks and deliverables depend on the service, but these are the areas I normally cover as a project moves from discussion to delivery.
01 / Discover — Consultation
I begin by understanding the business need, the current situation and the outcome you are trying to reach. For an existing website or system, this can include the current platform, hosting, CMS, integrations, workflows and known issues.
- Review the current website, system or business requirement.
- Understand the audience, services, content and primary goals.
- Identify important technical limitations, dependencies or known problems.
02 / Plan — Proposal & scope
I turn the requirement into a clear direction before the main work begins, separating essential requirements from optional improvements and identifying the dependencies that affect delivery.
- Define the agreed scope, deliverables and priorities.
- Identify access, platform, content and integration dependencies.
- Confirm the practical approach, timeline and investment.
03 / Build & Review — Development & review
I carry out the agreed work in structured stages with attention to usability, technical quality and maintainability. I then review the important areas, test what matters and make the agreed refinements before final delivery or launch.
- Build the agreed pages, functionality, integrations or technical improvements.
- Review responsive behaviour, forms, links, permissions and interactions where relevant.
- Test project-specific dependencies and resolve agreed issues before release.
04 / Support — Launch & ongoing support
After approval, I complete the launch, deployment or handover and verify the result. If ongoing help is needed, I can continue with maintenance, improvements, SEO, technical operations or future development.
- Coordinate launch, deployment or final handover.
- Verify important production dependencies after release.
- Continue with maintenance, improvements or technical support when needed.
What I need from clients
Support for the systems that sit behind the public website.
You do not need to arrive with a technical specification, but timely information, access and decisions help the project move efficiently.
Accurate business information
Clear service, product, audience and content information so the work is based on the real business requirement.
Required access
Timely access to domains, hosting, CMS accounts and third-party platforms when the project depends on them.
A clear decision-maker
One person who can confirm priorities and provide approvals when decisions are required.
Consolidated feedback
Practical feedback grouped into clear revision rounds rather than conflicting comments from several directions.
Important constraints early
Known deadlines, integrations, platform restrictions or business requirements should be shared as early as possible.
Realistic production coordination
Launch or deployment timing should account for access, DNS, third-party approvals and other external dependencies where applicable.
Have a project that needs a clear starting point?
Tell me the current situation and the outcome you are trying to reach.
You do not need to define the technical solution first. Share what exists, what is not working or what you want to create, and I can help identify the likely scope, dependencies and next step.