Clear answers to what people ask

It is the digital version of the discovery meeting we would otherwise hold with you. Everything we would normally cover in a two-to-three hour session, modules, roles, permissions, integrations, automations, reports, data migration and design, is collected through short, adaptive questions. You write, we draw out the scope.

Most projects grow, and get expensive, because someone says "and could it also do this" halfway through. We settle the scope up front: which modules, who sees what, what needs approval, which systems must talk to each other, which reports matter. Once the brief is complete we hold a build-ready roadmap, so the system can be delivered correctly in a single pass.

Anyone can browse the form, but filling it in needs a code issued to you. There are two reasons: every brief that arrives is read end to end by a real person, so the code keeps spam and fake submissions out; and it lets us match your brief to your record and prioritise it. No code yet? Use "Get in touch" and we will send one within minutes.

Usually 6-12 minutes. Each screen holds at most two questions, and the flow shrinks based on your answers, so nothing irrelevant is asked. Your answers are saved in your browser, so you can stop and pick up where you left off on the same device.

That is fine. "Not sure yet" is a valid answer, and optional fields can stay empty. We close the gaps together in the follow-up call; the brief exists to speed up the conversation, not to test you.

The brief reaches our team immediately. We turn your answers into a project scope with the modules needed, the technical approach, an approximate timeline and an investment range. We usually get back to you within one business day, on the channel you picked in the form (WhatsApp, phone or email).

No. "Build your own" lets you combine CRM, ERP, a website, an online store, SaaS, an AI chatbot and SEO into one package. Shared questions (your company, your team, your priority, contact details) are asked only once, and each piece adds only its own module screen. We also ask, in one question, how the pieces should connect.

Every module screen has a "custom module" field: describing it in your own words is enough. Most of our work is exactly this, the company-specific flows that fall outside ready-made packages. From subcontract production tracking to pricing by square metre, any bespoke process can go into the system.

Yes. In the form you can pick your colour world, enter your brand hex codes (like #1A1A1A), and set your typeface and the tone of your brand. If you do not have an identity yet, choose "you decide" and we will propose a palette and typography that suits your brand.

Your answers travel over an encrypted connection straight to the dyrdev. team; they are not shared with third parties or sold for marketing. An unfinished draft lives only in your own browser for 24 hours and is deleted the moment the brief is sent. We never ask for sensitive data (passwords, card details, ID numbers), so please do not enter any either.

No, we do not quote automatically. After reading the scope we come back with a realistic range and an explanation of what costs what and why. The budget question in the form is entirely optional; leave it blank or choose "let's discuss".

No. The timing question is for planning only; it is not a delivery promise. We agree the real schedule together once the scope is settled, and put it in writing.

Yes. We can meet on site in Kocaeli, İzmit, Gebze and the surrounding districts, and we work remotely with clients anywhere in Türkiye. Meetings run over the phone, on a video call, or through WhatsApp.

Once the scope is settled, the work is split into stages. It usually runs as a deposit at the start, then instalments at interim deliveries and at launch. All terms are set out in the written contract.

Yes. After launch we set up a separate support arrangement for fixing, monitoring and further development. Its scope and duration are agreed in writing up front.

Code developed and paid for under the contract belongs to you. Domain and server accounts are opened in your name too, so you never depend on us.

In most cases yes. We first review the existing code and infrastructure and give you a clear assessment of whether it can be taken over; where taking it over does not make sense, we say so plainly.

Yes. Scope, delivery stages, the payment plan, intellectual property and support terms are all settled in a written contract. The brief form alone does not take the place of a contract.

Yes. We migrate customer, quote and order records out of Excel, CSV, Google Sheets and most legacy CRM/ERP databases. Duplicates are cleaned up and the matching rules are agreed with you.

We do not charge a licence per user. The same architecture serves a team of five and an organisation of a hundred; as the scale grows, only the server resources are planned accordingly.

Once the scope is settled through the brief, a typical CRM rollout goes live in about a month. The timeline shifts with the number of modules and the integrations needed.

No. We build the ERP to work alongside the accounting software you already use. Invoices and ledger movements flow automatically between the two systems, and your accountant stays on the screen they know.

That is our starting point rather than a problem. Subcontract production, calculation by square metre or weight, multi-level recipes and bespoke quality criteria are modelled into the system directly.

Yes. Warehouse and production screens are designed to work on tablets and phones: scanning a barcode, uploading a photo and closing a work order can all be done from the floor.

Either way works. Send us the copy and we edit and place it; if there is none, we write it for your sector and put it in front of you for approval.

Yes. We move the content and blog posts across and, if the URL structure changes, set up the redirects, so you do not lose the rankings you already have.

We set everything up through accounts opened in your name. The domain and the server stay your property, so you never depend on us.

If your needs are standard, a ready-made package will do the job, and we will say so plainly. The moment you need variants, dealer pricing, a bespoke calculation or an unusual integration, you hit the package's ceiling. A custom build has no such ceiling.

We build to scale from a few hundred products to tens of thousands. As the catalogue grows, the search, filtering and stock-sync architecture is planned to match.

Yes. Orders from marketplaces arrive in your own panel, stock is managed from one place, and shipping runs through the same flow.

Yes. In that case the first job is turning the idea into a scope: who will use it, what job it solves, what goes into the first release. We do not write code before that is clear.

The product code developed and paid for under the agreement is yours. Repository access, documentation and the handover process are planned from the start.

Yes. We set up a separate support arrangement for monitoring, fixing and building new features after go-live.

The bot only answers from the sources you provide. Where it is unsure it is built to hand the subject to your team rather than invent an answer, and it is tested scenario by scenario before launch.

Yes. We set it up on the WhatsApp Business API using your own number, so your customer never has to write to a different one.

Yes. We connect it to read order, stock and customer information from your own system, so the bot answers with real data.

The effect of technical fixes can show within a few weeks. Ranking gains driven by content usually become clear between three and six months in. We would advise against trusting anyone who guarantees a position on day one.

No. Ranking depends on the search engine's algorithm and nobody can guarantee it. What we commit to is transparent reporting of the work done and measurable progress.

GEO is structuring content so AI tools can understand it and cite it as a source. Clear definitions, question-and-answer blocks, and current, verifiable data are the foundation of that work.