Questions, answered.

I'm Giorgi Grdzelidze — a fullstack web developer based in Tbilisi, Georgia, focused on Laravel + Vue.js applications. I take projects from database design through to a polished public surface, usually as a solo engagement.

Tbilisi, Georgia (UTC+4). I overlap comfortably with Europe and the Middle East during a normal working day, and with the US East Coast in the late afternoon.

I communicate fluently in Georgian, English, and Russian. Code, commits, and documentation are written in English by default; product copy and admin labels can ship in any of the three.

Currently I take on contract and project-based work alongside ongoing client commitments. Short audits, focused builds, and longer multi-month engagements all fit — get in touch with a rough scope and I'll tell you honestly whether the timing works.

Yes — happy to sign a mutual NDA before any sensitive technical or business detail is shared. Send your standard form, or I can provide a simple one if you don't have it ready.

Both. Well-scoped builds with a clear deliverable work as fixed-fee. Ongoing engineering, audits, and code review run hourly or on a weekly retainer. We agree the structure together after the discovery call.

For full builds I usually start around a one-week engagement; smaller asks (a focused audit, a code review, a tricky bug fixed) can be a few hours. If a request is below the threshold I'll say so and point you toward someone who fits better.

USD and EUR for international clients, GEL for Georgian clients. Wire transfer, Wise, and direct bank deposit are all supported.

For fixed-fee projects: 50% up front, balance on delivery. For retainers and hourly work: invoice at the end of each two-week cycle, net 14. Larger engagements can be split into monthly milestones.

No. The first 30–45 minutes are on me — enough to understand the problem, share an honest read on feasibility, and decide together whether moving forward makes sense.

A short discovery call (or written brief) to align on scope, constraints, and success criteria. From there I send a written proposal with timeline, deliverables, and price. Once accepted, work starts on the agreed kickoff date — typically within one to two weeks.

Async-first by default — Slack, Notion, or email for day-to-day updates; one short weekly sync (15–30 minutes) to align on direction and unblock anything pending. Major decisions go into a written log so nothing gets lost.

A focused marketing site or admin panel: two to six weeks. A bespoke SaaS feature or finance module: one to three months. A full end-to-end product: three to six months. Estimates tighten after the discovery call.

Each milestone includes a review window for feedback within the agreed scope. Changes that fall outside scope get re-estimated as a small change request — no surprises on the invoice. The goal is to keep the door open without re-opening every decision.

Yes. Every project ships with a 30-day warranty window where any defect against agreed scope is fixed at no charge. Beyond that, ongoing support runs as a retainer or hourly bank — your call.

Laravel 11+ and PHP 8.3+ on the backend, Vue 3 + TypeScript + Inertia.js on the frontend, Tailwind CSS for styling, Filament for admin panels. MySQL or PostgreSQL for data, Redis for cache and queues. CI on GitHub Actions, Pest for tests.

Laravel is the default — it's where I'm fastest and most opinionated. I can integrate with Node.js or Python services where they already exist, but I won't pretend to be the right person to greenfield a Django or Rails app.

Both. About half my work is on legacy or partially-built Laravel projects — refactors, feature additions, performance fixes. I start with a short audit pass so we both know what we're dealing with before estimates get written down.

Translatable JSON columns via Spatie's package, per-locale slugs and meta, locale-prefixed routes, fallback chains for missing translations, and proper hreflang + canonical URLs for SEO. The admin panel surfaces every translatable field with tabbed locale switching so editors don't get stuck.

You do — fully, from day one. Code lives in your GitHub (or wherever you prefer), under your account or organisation. I don't keep private mirrors. On project close I revoke my own access unless you specifically want me available for ongoing support.

I set up CI/CD pipelines and write deploy procedures, but I don't run hosting on your behalf. Recommended targets: Forge, Vapor, Hetzner Cloud, or Fly.io depending on scale and budget. I'll do the initial deploy with you and document it so your team (or future me) can repeat it.