FAQ and key terms in plain words
Answers to common questions about work, timelines, access and payment — plus a short glossary explaining D7, REST, webhook, HL block and other terms.
FAQ
Do you work under a contract?
Yes, officially as a sole proprietor: contract, invoice and closing documents.
Do you work with the Bitrix24 box (D7)?
Yes. I customize the boxed version: modules, business processes and direct integrations on D7.
Do you work with the Bitrix24 cloud?
Yes. For the cloud I build apps and integrations via REST API and webhooks.
Do you take over a legacy project?
Yes. First an audit and a problem map, then careful fixes without stopping the business.
How does the work start?
With a short diagnostics: I review the task and assess risks, timeline and cost.
How is the cost calculated?
Hourly or by an hour package (packages are cheaper). The exact estimate comes after the diagnostics.
Is there support after release?
Yes. I support, fix by logs and develop the solution after launch.
Can we start without a full spec?
Yes, if there is a clear problem. I first run diagnostics and form a plan.
What is needed for an estimate?
A problem description, links/screenshots and access to a test environment or logs if the task is about errors.
Do you handle urgent tasks?
Yes, but urgency affects the cost and depends on the current workload.
Can you improve someone else's code without a rewrite?
Yes, if the architecture allows. I first record risks and entry points.
Do you do DevOps?
Basically I prepare the environment for my own solutions: deploy, logs, GitHub Actions, Nginx. Full infrastructure support — separately or via a DevOps specialist.
Can we work on a retainer?
Yes, if you need a regular volume of tasks, support and CRM/backend development.
What if something breaks after release?
If the cause is in my work — I fix it within the warranty period. If it is in an external service or new requirements — I estimate it separately.
In plain words
- D7
- development inside boxed Bitrix24.
- REST
- data exchange between systems via an API.
- Webhook
- an event a system sends out on a change.
- Queue
- heavy operations run in the background and do not slow the main process.
- Retry
- an automatic retry of a failed operation.
- Payload
- the data that came in or went out of an API.
Not sure where to start?
Just describe the problem. I will study the current solution, assess the risks and propose implementation options.