From first call to delivered hours.
A typical engagement moves through four phases. Onboarding is structured to take two to three weeks; steady-state runs indefinitely on a monthly cadence.
Engagement model
One contract, hourly billing, monthly acceptance.
Every DSJ engagement runs on the same template. Defined scope, two-tier hourly compensation, documented monthly acceptance, predictable invoicing. The mechanics are simple by design - the value comes from running them consistently.
Engagement lifecycle
01
Scoping call
30-minute conversation. We learn what's eating your operational bandwidth, which domains might fit, what's been tried, and where the constraints are. No pitch deck, no proposal pressure. If the engagement looks viable for both sides, we move to scope drafting.
02
Scope and agreement
Written scope document defines services, monthly hour packages, acceptance criteria, communication routines, and rate tiers. Counterparty due diligence runs in parallel. Service agreement is signed under Georgian law before any work starts.
03
Onboarding and kickoff
Account access, documentation handover, communication channel setup, kickoff meeting with the assigned specialists. The first billing period begins on the kickoff date and runs to month-end.
04
Steady-state monthly cadence
Specialists work the agreed hours across the agreed domains. Weekly running log of work in progress. Month-end Service Acceptance Protocol documenting delivered hours and confirming acceptance. Invoicing follows acceptance.
Compensation
Two-tier hourly model.
All DSJ engagements run on hourly compensation against a monthly hour package. The two-tier structure separates routine capacity from extended capacity, so scope expansion is visible and priced upfront rather than discovered at month-end.
T1
Base monthly package
A defined block of hours per month at the base rate. Covers routine operational work across the agreed domains. Established in the service agreement and adjusted only in writing.
T2
Extended package
Hours above the base threshold, billed at the extended rate. Used when scope spikes - launches, migrations, incidents, expansion phases. Activation is acknowledged in writing before extended hours are logged.
Specific rate tiers, hour thresholds, and rounding conventions are confirmed in the service agreement. The two-tier model is consistent across engagements; only the parameters change.
Acceptance protocol
How each billing period closes.
Every billing period ends with a Service Acceptance Protocol - a short document that records what was delivered, how many hours were used, and whether the work has been accepted. Invoicing follows acceptance, never precedes it.
What the protocol contains
- Period covered (typically one calendar month).
- Domains worked and major work items delivered.
- Hours logged against the base package and against extended capacity, separated.
- Acceptance confirmation by the client representative.
- Notes on disputed hours or items requiring clarification, if any.
Why this matters
The acceptance protocol is not a procedural overhead. It's the operational record that lets long-running engagements stay clean over years. Disputes get resolved at month-end on a single document instead of accumulating into year-end reconciliation.
For clients with audit, board, or due diligence obligations, the accumulated stack of signed acceptance protocols becomes the operational record - what was delivered, when, at what cost, with what acknowledgement.
Communication
How clients work with us day-to-day.
Three layers of communication, each calibrated to the work at hand. Predictable rhythm at the operational level, on-call response for incidents, structured review at the engagement level.
Operational layer
Daily and weekly cadence
Day-to-day work runs through whatever channel the client uses - shared inbox, ticketing system, project board, chat workspace. Weekly running log of work in progress, surfaced through the agreed channel.
Incident layer
Defined response windows
For things that break or need urgent attention, the engagement defines a response window - typically same-day for severe issues, next-business-day for routine. Escalation paths are agreed in advance.
Engagement layer
Monthly review and acceptance
Month-end review where delivered hours, completed work, and any open issues are discussed. Acceptance protocol signed at this point. Quarterly check-ins to recalibrate scope if the operational mix is shifting.
Governance
The contractual frame.
DSJ engagements are anchored in a structured service agreement under Georgian law. The legal frame stays consistent across clients; only the operational parameters change.
01
Bilateral service agreement
Standard agreement template, executed under Georgian law. Sets out services, hour packages, rates, acceptance criteria, payment terms, confidentiality, and termination.
02
Independent contractor model
DSJ operates as an independent contractor. Equipment, software, and operational infrastructure are provided by DSJ. The engagement creates no employment relationship.
03
Confidentiality framework
Standard confidentiality terms cover client information, operational data, and project specifics. Terms run for seven years from end of engagement, or indefinitely for sensitive categories.
04
Liability and dispute
Standard limited liability provisions. Dispute resolution by arbitration or competent courts as defined in the agreement. Governing law: Republic of Georgia.
Engagement end
How engagements end cleanly.
Engagements end when they end. Maybe the operational work is no longer needed; maybe the relationship has run its course; maybe scope has shifted in a direction we don't cover. We design endings to be as clean as the beginnings.
Standard termination notice is one calendar month. The final billing period closes with a normal acceptance protocol. Account access is handed back, operational documentation is consolidated and transferred, and a closing summary documents the state of in-flight work.
Confidentiality survives termination. Specialists who worked on the engagement remain bound by their own confidentiality agreements with DSJ.
Get in touch
See if the model fits your operation.
First conversation is a 30-minute scoping call. We'll walk through the model, hear what you need run, and tell you whether we're the right partner for it.