Contact DarDev Services by email at contact@dardev.net, through the contact form on news.dardev.net, or via the services page at dardev.net/services. Every inquiry routes to our Twenty CRM queue so nothing sits in a personal inbox. We reply to well-scoped consulting requests within two business days; vague "we need DevOps help" messages usually get a short checklist before we schedule discovery.
DarDev Services covers cloud migration, DevOps, custom software, and integrations for MENA teams—separate from Hesabi (Tunisia-only invoicing), DarDevLab (labs), and EscaHire (waitlist). Fiscal software for a Tunisian PME starts at hesabi.tn; production hardening or custom delivery starts here.
Where to send your first message
- dardev.net/services — best for consulting and delivery scoping; link your architecture sketch if you have one
- news.dardev.net contact form — enterprise platform, partnerships, press, or when you found us through an article
- contact@dardev.net — direct email when attachments or thread history matter; same CRM routing as the forms
- LinkedIn messages — fine for a warm intro, but we still ask for a written brief before quoting
We operate from Tunis with remote delivery across MENA. You do not need a local entity to start a conversation—regulated workloads may later need explicit data residency documentation.
What to include in your first email
A useful first message saves a week of back-and-forth. We are not asking for a polished RFP—redacted pipeline YAML beats a marketing deck—but we do need enough context to know whether DarDev is a fit and who on our side should join the call.
- Company name, sector, and country where production data must live
- One-paragraph problem statement: what breaks today or what deadline is driving the ask
- Current stack summary: host (OVH, AWS, Azure), runtime (Compose, K8s, VMs), CI tool, primary database
- Team shape: internal engineers available for pairing, and who owns outcomes after we hand off
- Timeline and budget range: even a rough monthly OPEX band helps us propose phased work instead of fantasy scope
- Attachments welcome: architecture diagram, failed deploy log, or backup schedule—mark anything confidential
Say if you are evaluating build versus buy—we redirect to Hesabi or DarDevLab when a product fits better than a services SOW. See custom-dev-vs-product-fit for how we decide.
What happens after you submit
- CRM triage (same day)
Inquiries land in Twenty CRM with source tags. We classify consulting vs product support vs press and assign an owner.
- First reply (1–2 business days)
For consulting fit, we acknowledge receipt, ask any missing checklist items, and propose one or two 30-minute discovery slots.
- Discovery call (free fit check)
We confirm pain, constraints, and whether your timeline matches our capacity. Deep technical review may move to a paid assessment.
- Written scope (within ~1 week after discovery)
You receive current-state notes, phased recommendations, effort range, and explicit out-of-scope items—same pattern as our DevOps scoping guide.
- Engagement start
Retainer, project SOW, or staff augmentation depending on the model that fits. Kickoff includes access, communication channel, and success metrics.
Response times and when we decline politely
Consulting inquiries: two business days. Partnership or press: three. Product questions: redirected within one. We pass on hardware-only NOC contracts, legal opinions, mismatched budgets, or problems a product already solves.
Scoping, pricing, and typical first engagements
We do not quote fixed migration or Kubernetes projects from a single paragraph email. First engagements are often bounded: a one-week paid assessment, an observability kickstart outline, or a hardening sprint on a known VPS stack. Read when-to-hire-dardev-cloud-migration for signals that external help beats DIY—those are the same signals we look for in your first message.
- Project-based: fixed SOW for MVPs, targeted migrations, or integration deliverables
- Retainer teams: dedicated pod with continuous backlog—our default for scale-ups
- Staff augmentation: senior engineers embedded in your team when you own the roadmap
Pricing depends on scope, seniority mix, and on-call requirements. We share ranges after discovery—not from a cold-email rate card.
Ready to start?
Send your stack summary and biggest operational pain to contact@dardev.net or use the form on dardev.net/services. Mention this article if it helped you prepare—we track which guides lead to good-fit conversations so we can keep improving them.
What is the fastest way to reach DarDev for consulting?
Email contact@dardev.net with company context, problem statement, stack summary, timeline, and budget range—or use dardev.net/services. All paths route to Twenty CRM.
How long until someone replies?
We target one to two business days for consulting inquiries. Incomplete messages may get a checklist first; complete ones move straight to discovery scheduling.
Is the first discovery call free?
Yes for fit and scope alignment. Deep dives with configs, restore drills, or written assessments are paid—and often credited toward the engagement if you proceed.
What should I attach to the first email?
Architecture sketch, deploy steps, backup schedule, or redacted error logs. Mark confidential material; we do not need production credentials in the first message.
Can DarDev help with Hesabi or TTN setup?
Hesabi is a product on hesabi.tn. DarDev Services can harden the infrastructure around fiscal workloads or integrate APIs, but SME invoicing support goes through Hesabi channels unless scoped as custom delivery.
Do you work outside Tunisia?
Yes—remote consulting across MENA and Europe-aligned zones. Data residency and subcontractor requirements are scoped explicitly per client contract.
