HOW WE WORK

A clean production system built for speed, quality, and predictability.

Spanix is not a freelance marketplace. We operate as a managed engineering, architecture, and design production team with clear inputs, checkpoints, QA, and submission-ready delivery packages. See our standards and services.

Principles
What you can expect from Spanix

Rules applied to every package — so you don’t waste cycles explaining basics.

Scope-first clarity

We confirm deliverables, format, standards, and deadlines before production starts. Scope changes are documented.

Inputs definedOutputs locked

QA before delivery

Every delivery is checklist-reviewed: naming, units, references, model discipline, and coordination logic.

ChecklistIssue log

Organized submission packages

You receive structured folders and clean files ready for client submission — no random exports or messy drafts.

FoldersTransmittal note

Professional communication

Short updates, clear questions, and one accountable contact per package to keep decisions fast.

Single POCWeekly update
Workflow
The delivery pipeline

From inputs → production → QA → final package. Simple steps, strong control across engineering and design disciplines.

1

Inputs & scope

Receive drawings/models/specs + confirm deliverables, formats, deadlines, and software environment.

2

Production

Work starts under internal rules: naming, units, layers, model discipline, and package logic.

3

QA checkpoint

Checklist review + issue log covering clashes, missing refs, inconsistencies, and assumptions.

4

Delivery package

Submission-ready folder with final files, logs, notes, and a clear handover package.

What the delivery package contains

  • Final drawings/models (DWG/PDF/IFC/NWC/Excel/Renders)
  • Revision log (what changed / what to review)
  • QA checklist ticked + exceptions noted
  • Issue list (RFIs / missing info / clashes)

Revision cycle (clear and fair)

  • Revisions = changes within agreed scope
  • Scope change = new deliverables or new areas
  • We confirm impact before proceeding
  • Every round documented in log
Quality
Our QA checklist includes

Practical checks — things that actually break projects if ignored.

  • File naming, numbering, versioning aligned with client system
  • Units, levels, coordinates, references validated (no silent assumptions)
  • Drawing readability: lineweights, tags, dimensions, legends, notes
  • Coordination logic: clashes, access, clearances, constructibility flags
  • BOQ consistency: quantities tied to model/drawings + takeoff method documented
  • Design presentation quality: sheets, visuals, and review sets prepared for client-facing use
Start a project
Send a brief (60 seconds)

Fill the essentials. Clicking “Generate Email” opens a ready-to-send scope email.

1) Choose service

Due date
Scope summary

2) Generate email

Email will include service + scope + due date + requested outputs.

Recommended inputs
PDF IFC Revit Civil 3D Tekla 3ds Max / Images
FAQ
Common questions

Short answers to remove hesitation and speed up decisions.

Do you sign NDAs and handle confidential files?
Yes. NDA-friendly workflow is standard. We can work with ACC/BIM360/Aconex/SharePoint access rules and controlled delivery logs.
What inputs do you need to start?
Minimum: PDFs or IFC. Best: native models (Revit/C3D/Tekla) + specs + any client template/standard. For visualization, images, references, or 3D files are helpful.
How fast can you start?
After scope confirmation, we can onboard within 24–48 hours depending on discipline and package size.
Can you scale multiple packages in parallel?
Yes. We can allocate dedicated teams per discipline and manage outputs under unified standards and package numbering.
FAQ

Everything clients ask — answered clearly.

Clear answers about pricing, confidentiality, inputs, turnaround, revisions, delivery structure, and how Spanix works with GCC and international clients.

Common questions

FAQ

Short answers that help decision-makers move forward faster and with more confidence.

Pricing NDA Turnaround Deliverables Revisions Workflow
How do you price your work? +
Pricing is quote-based. We price according to scope size, complexity, input quality, output format, deadline, and review requirements. After reviewing your brief, we send a clear quote and delivery plan. If scope changes, we document the impact before proceeding.
Do you offer fixed price packages? +
Yes — for well-defined deliverables such as BOQ packages, takeoff logs, clash reports, drawing updates, or focused design boards. For larger or evolving scopes, we usually recommend a staged quote or a dedicated delivery setup.
Can you sign an NDA? +
Yes. NDA is standard for us. You can send your NDA template, or we can provide a simple NDA format. We also keep samples and case references client-safe unless public use is explicitly approved.
What inputs do you need to start? +
Minimum: latest PDF drawings and specs. For coordination-heavy work, IFC, Revit, Civil 3D, or Tekla inputs are highly preferred. If your inputs are incomplete, we can still start by documenting assumptions and open items clearly.
What is your turnaround time? +
Turnaround depends on scope, package size, and review cycle. Once scope is confirmed, we provide a practical timeline. If you have a hard deadline, tell us early so we can propose prioritization or staged delivery.
How many revision rounds are included? +
For smaller fixed packages, we عادة include one revision round based on consolidated feedback. For recurring or larger scopes, revisions are handled through issue logs and controlled delivery cycles.
How do you deliver files? +
We deliver a submission-ready package with organized folders, delivery note, revision log, and outputs in the required format such as PDF, DWG, IFC, Excel, boards, or renders. We can also align to client platforms like Aconex, Asite, ACC, or SharePoint.
Can you match our drawing or BIM standards? +
Yes. Share your naming rules, templates, CAD standards, or BIM execution requirements, and we align our outputs accordingly to reduce review friction and improve approval speed.
Do you work with consultants, contractors, or developers? +
All three. We support consultant deliverables, contractor production support, and developer-facing documentation. The important part is defining the package, review path, and output expectations clearly.
What payment terms do you use? +
Terms depend on scope and working relationship. For new clients, we usually agree on milestone-based terms. For recurring work, monthly invoicing or package-based billing can be arranged.
Can you work as an extended remote team? +
Yes. For recurring scopes or parallel packages, we can operate as an extended production team with lead oversight, QA checkpoints, reporting rhythm, and delivery discipline aligned with your internal workflow.

Quick question

Ask us directly

Fill the fields and click “Generate Email”. Or use WhatsApp for faster coordination.

Destination email is set to hello@spanixengineering.com. Attach files if your question relates to a real package or project.