Skip to content
N1

How I work: process, risks and scope

A transparent process: how I organise the work, why projects break and how I avoid it, what is and isn't included, how I reduce risks — plus the integration scheme for cloud and boxed setups.

How we work

01

Intro and audit

I study the task, the current solution and the processes.

02

Timeline and cost estimate

A transparent estimate by scope of work.

03

Signing the contract

I work officially, under a contract.

04

Prepayment

We fix the terms and start the work.

05

Development

Implementation with logs, tests and documentation.

06

Result demo

I show a working solution.

07

Final payment

Payment upon acceptance.

08

Support

Support and development after release.

Why projects break

No logging No tests No documentation Integrations work directly Business logic is scattered across the project No error control

This is usually exactly what I fix.

How I do it
A separate service layer
Logging of incoming and outgoing requests
Secret masking
Retry and error handling
Documentation of entry points
Test scenarios
A clear project structure
Separate tasks for tech debt

What the work includes

  • Task analysis
  • Development
  • Logging
  • Documentation
  • Testing
  • Launch help
  • Post-release support

What is not included by default

  • Administration of the client's entire infrastructure
  • Responsibility for failures of Bitrix24, MoySklad, 1C, WhatsApp providers and other external services
  • A full rework of the old architecture without a separate estimate
  • Round-the-clock support without a retainer agreement
  • Work without access, logs or a test scenario

How I reduce risks

  • Diagnostics first
  • I do not touch production blindly
  • I record changes
  • I do not log secrets
  • I make backups when there is a risk
  • I leave documentation
  • I work through tasks
  • I do not promise an exact price without access to the problem

What the client gets after the work

  • A working improvement
  • A clear verification scenario
  • A short description of changes
  • A list of affected files/modules
  • Logs or diagnostic points
  • Recommendations for further development
  • An understanding of what to do on a repeat error

Integration scheme

Depends on the Bitrix24 edition

Bitrix24 Cloud

Integrations go through the Laravel Hub: REST API and webhooks.

Bitrix24
Laravel Hub
1C MoySklad TrustMe PKB ADATA Telegram
Bitrix24 D7 (box)

Integrations are implemented directly inside the portal on D7.

Bitrix24 · D7
1C MoySklad TrustMe PKB ADATA Telegram

Not sure where to start?

Not sure whether you need REST, D7 or a separate backend? I will describe the approach after a short review.