Services
What you get, in plain terms.
Two services. They are sold separately, they are priced separately, and they are worth more together because the second one is drawn from the first.
Websites that ship
Design and build, start to finish. A real Next.js application on a real server — not a page builder you outgrow in a year.
- Design and build, from blank page to live domain
- A CMS your team edits without calling me
- Booking, quotes and contact flows that reach a human inbox
- Two languages where the market needs two languages
- Search, speed and accessibility handled during the build, not bolted on
- Server set up, documented, and handed over
Social design that keeps up
Launch is when the content problem starts. Monthly packs of post, story and ad graphics built from your site’s own design system.
- Monthly packs: feed posts, stories, ad creative
- Built from the site’s type, colour and grid — one company, one look
- Editable templates, so your team can keep going between packs
- Every format at its native size, no stretched crops
- Ad variants for testing, not one image resized four ways
- Turnaround measured in days
How it goes
Four steps, no surprises.
A call
Twenty minutes. What you sell, who buys it, and what is currently in the way. If I am not the right person for it, I will say so on this call.
A written scope
What gets built, what it costs, and the date it is done. Fixed price. You approve it in writing before anything starts.
The build
A staging link from the first week. You watch it come together and correct course early, instead of waiting for a reveal at the end.
Handover
Repository, accounts, documentation and a walkthrough recording. You could hire anyone to take it from here — that is the test a handover has to pass.
Tools
What I build with.
- Interface
- Next.js
- React
- TypeScript
- Tailwind CSS
- GSAP
- Backbone
- Node.js
- PostgreSQL
- Prisma
- Sanity
- Resend
- Design
- Figma
- Photoshop
- Illustrator
- After Effects
- Delivery
- Linux VPS
- Nginx
- Cloudflare
- GitHub Actions
Before you ask
The questions that actually decide this.
You are in Istanbul. How does that work day to day?
My working day covers all of yours if you are in Europe, and your morning if you are on the US East Coast. Calls are booked at your hour. Between calls, everything runs through email and a shared staging link, so nothing waits on us being awake at the same time.
Who owns the code and the accounts?
You do, from the first commit. The repository is created under your account, the domain and hosting are registered in your name, and I work as a collaborator. If we stop working together, nothing needs to be transferred, because nothing was ever mine.
How does payment work?
Fixed price agreed in writing before the work starts, split into a deposit and a payment on delivery. Invoices in USD or EUR, paid by bank transfer or Wise. Larger builds are split into milestones so you are never paying far ahead of what is finished.
What happens after launch?
Thirty days of fixes included — anything that does not work as specified, I fix. After that you can leave it alone, take a monthly social design pack, or bring me back for changes at an hourly rate. There is no mandatory retainer.
We already have a brand. Can you work inside it?
Yes, and it makes things faster. Bring your logo, colours and fonts and I will build the system around them. If what you have is a logo and nothing else, that is normal, and defining the rest is part of the work.
How long does a site take?
A focused marketing site is four to six weeks from approved scope to live. Anything with accounts, bookings or a catalogue behind it runs longer, and the scope document will say exactly how much longer before you commit.
Pricing
Quoted per project, never per hour guessed at.
Every project gets a written scope with a fixed price before any work starts, so you are approving a number rather than watching a meter. Tell me what you need and I will send that scope — it costs nothing and takes a day.