Start a project
You don't need a specification, a budget or the right vocabulary. A description of the problem is enough — the shape of the solution is the studio's job, not yours.
Enquiry
marianvanghelie66@gmail.com
Perfectly acceptable. Two lines about the problem is a fine first message.
A reply within one working day, then a short call at a time that suits you. If the project makes sense, you'll get a written proposal with a fixed scope, a fixed price and a delivery date. If it doesn't, you'll be told that too — usually along with what to do instead.
Welcome, and routine. Projects have run in English, Romanian and Spanish across the UK, Romania and Spain. Time zones have never been the difficult part of a project.
A focused landing page and a multi-role operations platform aren't the same purchase, so there's no menu price. You'll get a written figure before any work begins, and it won't move unless you change the scope.
A first working version usually appears within one to two weeks of starting. Websites often complete inside two to three weeks; applications typically run four to eight, depending on how many people and permissions are involved.
Yes — code, repository, domain, hosting and database accounts. Set up in your name where possible and transferred where not. You should be able to hire anyone else tomorrow without a hostage negotiation.
Usually, and often that's the cheaper answer. Plenty of engagements are improvements, integrations or rescues rather than rebuilds — a rebuild only gets recommended when it genuinely costs less than the alternative.
No. AI appears where it clearly outperforms ordinary code — reading messy documents, drafting, classifying — and stays out of everything else. Several of the best projects here contain none at all.
That's the normal starting point. The first conversation exists to turn a vague, irritating problem into a specific, costed one — and you're free to stop there.