You have a project to deliver
You need a website, custom feature or integration. Bring your goals, current setup and constraints; we turn them into an agreed scope.
Explore WordPress development ↗INDEPENDENT DEVELOPER · UK & EUROPE
Your brief. My full attention.
Work directly with the person building your website. I help businesses and agencies turn a WordPress brief into a defined project, with visible progress and a practical handover.
Based in Istanbul. UK working-day overlap.
Available for suitable projects worldwide.
START WITH YOUR SITUATION
You need a website, custom feature or integration. Bring your goals, current setup and constraints; we turn them into an agreed scope.
Explore WordPress development ↗You lead the client relationship. I deliver the agreed WordPress work within your review process, with white-label arrangements discussed before kickoff.
See agency collaboration ↓Something is broken, unfinished or difficult to maintain. Start with a review of the actual site and code, then agree the next useful change.
Describe the problem ↗HOW WE WORK TOGETHER
One named developer, a written plan and review points that fit your team. Decisions and scope changes stay visible throughout the project.
Share your site, desired change, target date and budget. We clarify the requirements and whether investigation is needed first.
Agree deliverables, price, responsibilities, feedback rounds and support coverage. Confirm availability before setting the start date.
Review the agreed work on staging. Check it against real content and workflows, with progress updates at the agreed cadence.
Run the agreed release checks and hand over source access, dependency notes and guidance. Record who handles future changes.
FOR UK & EUROPEAN AGENCIES
Bring the approved design, technical brief or backlog. We agree where I fit into your team, how reviews happen and how work reaches your client.
Your project lead stays informed. Client contact, tools and meeting windows are agreed before kickoff.
Share NDA and presentation requirements early. Agree how the work is credited and what can appear in a portfolio.
Define repository access, review responsibilities, launch ownership and the notes needed for your team to continue.
COST, SCOPE & AVAILABILITY
UK projects receive a GBP proposal. Cost follows the actual requirements, existing code, integrations and handover needs. Timing also depends on content readiness and review turnaround.
A fixed quote for an agreed scope, with milestones, dependencies and a process for approving changes.
When the cause or effort is unclear, agree the purpose, fee and output of a focused review before committing to a build.
Discuss a prioritised queue and available capacity. Agree delivery and support expectations for that arrangement.
BEFORE YOU COMMIT
Public products and documentation give you something concrete to inspect. For your brief, we can discuss relevant implementation choices and how the work would be checked.
A product-pricing plugin with documentation covering currency conversion, rounding and order behaviour.
Read the documentation ↗Explore the language-management product and its published features, then ask how your editing and integration needs differ.
Explore the product ↗BEFORE WE TALK
I am based in Istanbul and work remotely with UK and European businesses and agencies. Calls, review times and launch windows are agreed around working-day overlap. Suitable projects from other countries are welcome.
I quote in GBP for UK projects after reviewing the brief and current site. A defined build can receive a fixed project quote. If the problem needs investigation first, that work is scoped and priced separately before it begins. The proposal records deliverables, dependencies, payment milestones and support coverage.
White-label collaboration can be arranged. Before work starts, we agree who talks to the client, where work is reviewed, how code is delivered and what can be shown publicly. Share any NDA requirements with the brief so they can be reviewed before confidential project material is exchanged.
Yes, subject to reviewing its current state. Share the site, known issues, existing scope and available documentation. I check the theme, plugins, hosting and code before recommending a focused repair, staged continuation or rebuild. Access and any paid investigation are agreed first.
The proposal defines the source code or repository access, deployment notes, dependency and licence list, and editor guidance needed for the agreed work. We also record account ownership, support responsibilities and any third-party restrictions so your team or another developer can continue.
Progress is reviewed against the agreed scope on staging. A new requirement is assessed for cost, dependencies and timing before it is added. You can approve a change, swap a planned item or keep it for a later phase. Decisions are recorded in writing.
Send your target date with the brief. I confirm availability and a realistic schedule after reviewing the work, content readiness, integrations and your review process. The proposal sets milestones and dependencies; a start date is confirmed when the scope is agreed.
A repeat development arrangement can be scoped around an agreed queue and available capacity. Routine updates, backups and monitoring belong in a care plan. Ongoing technical SEO, content and enquiry improvements belong in a separate SEO engagement. Support hours and response expectations are agreed for each arrangement.
Start with the public products and documentation linked on this page. Bring a specific problem and ask about the implementation, trade-offs and checks it needs. We can review relevant work together and define a small first milestone where that is useful.
LET'S START WITH YOUR BRIEF
Send your URL, the change you need, budget range and target date. I will review the brief and outline a suitable next step.