How we work
Fourteen days.
A team that works like your own.
The first recurring deliverable is running before day fourteen. After that, full operations with a dedicated team, stable assignments, and weekly reports — no rotation, no re-explaining the project every time.
The 14 days
Five stops. Fourteen days.
From kickoff to full operations, with every recurring deliverable running inside fourteen days. In-flight jobs are not paused; operations are stood up in parallel.
Day 0
Kickoff call
A one-hour session, during U.S. Eastern business hours. We review your active portfolio, current jobs, and the most urgent bottlenecks.
Days 1–3
Credentials and NDA
We sign a mutual NDA before touching anything. Each team member receives individual credentials with mandatory 2FA. No one shares access.
Days 4–7
Template mapping
We learn your estimating templates, your portfolio, your subcontractor network, and your end-client communication style. Nothing is reinvented.
Days 8–10
First estimates
The first recurring estimates go into production. In-flight jobs are not paused — operations are stood up in parallel, not in series.
Days 11–14
Full operations
Estimates twice a week, schedule maintenance, and recurring invoicing up and running. The first weekly touchpoint closes inside the second week.
Day 0
Kickoff call
A one-hour session, during U.S. Eastern business hours. We review your active portfolio, current jobs, and the most urgent bottlenecks.
Days 1–3
Credentials and NDA
We sign a mutual NDA before touching anything. Each team member receives individual credentials with mandatory 2FA. No one shares access.
Days 4–7
Template mapping
We learn your estimating templates, your portfolio, your subcontractor network, and your end-client communication style. Nothing is reinvented.
Days 8–10
First estimates
The first recurring estimates go into production. In-flight jobs are not paused — operations are stood up in parallel, not in series.
Days 11–14
Full operations
Estimates twice a week, schedule maintenance, and recurring invoicing up and running. The first weekly touchpoint closes inside the second week.
Weekly touchpoints
Monday
Written status
A brief progress report, pending payments, and exceptions, emailed before Eastern noon.
Wednesday
30-min call
Only when there are change orders, pending decisions, or exceptions that need a conversation — not by routine.
Friday
Weekly snapshot
A look ahead at the coming week: jobs, milestones, and confirmed subcontractors. Built to be read in two minutes.
Coverage
How we reach your portfolio — and when.
Three operating agreements that hold the day-to-day up: shift overlap with your time zone, a clear async window for non-urgent items, and a weekly sync with your subcontractor network.
Shift overlap
Mon – Fri · 9–18 ET
Daily base during U.S. Eastern business hours, with guaranteed overlap with Argentina and Europe. If you open a job at 9 AM Eastern, the team has it in hand before you’re back at the desk.
Async window
< 4 business hours
Non-urgent email and messages get a reply inside the agreed async window. Urgent items escalate to the Wednesday call; non-urgent items never dissolve into the inbox.
Weekly subcontractor sync
Monday · 10 AM ET
The team runs the Monday sync with your subcontractor network: schedule confirmation, pending-license unblocks, and scope questions resolved before they turn into exceptions.
Dedicated team, no rotation
Same names. Same team. Your company.
One team works on your portfolio — not six anonymous people answering tickets. The names you see on the estimate, the schedule, and the invoice are the same names every week.
We assign a fixed team to the client from kickoff: one person responsible for recurring estimates, another who maintains portfolio and schedule, and a single coordinator available for decisions. You know their names in the first week; the same roster is in place six months later.
No overlapping shifts, no rotating freelancers, no re-explaining the project to every new arrival. If someone leaves, we replace them within two weeks and walk you through the handoff — you don’t find out via a temporary dip in quality.
What you keep · What we absorb
Your day-to-day operational load: essentially nothing.
We define in writing what the team absorbs and what comes back to you for decision. The table is the standard operating contract — adaptable in the initial audit.
| Activity | Owner | Clarification |
|---|---|---|
| Recurring estimates, twice a week | Contramarco | — |
| Coordinate subcontractors and keep the schedule up to date | Contramarco | — |
| Portfolio maintenance and recurring invoicing | Contramarco | — |
| Deposit tracking and change-order processing | Contramarco | — |
| End-client communication, inside the software you already use | Contramarco | — |
| Weekly per-job progress reports | Contramarco | — |
| Approve change orders when the impact exceeds the agreed threshold | You | Comes to you with options, not open questions. |
| Provide credentials and portfolio access under NDA | You | — |
| Attend the weekly touchpoints (designed to last minutes) | You | — |
| Decisions on regulatory exceptions or non-budgeted spend | You | — |
Failure modes
What we absorb. What we send back to you.
Office work has its own failure modes. We define upfront which ones get resolved inside the team and which ones come back to you for a decision — with judgment, not as a line in the next report.
What we absorb
- Transcription errors between the estimate and the purchase order — we correct them without you having to ask.
- Quote delays when a subcontractor doesn’t respond on time — we reopen the request and escalate on our own.
- Missed follow-ups on outstanding deposits — the system flags them and we push them forward.
- A schedule that drifts on minor changes — we keep it current without escalating unless there’s real impact.
What we escalate to you
- A change order that moves the price beyond the agreed threshold — it comes back to you for an explicit decision.
- A dispute with the end client over scope interpretation — we escalate it with options, not open questions.
- A regulatory or permit exception that blocks the job — communicated immediately, not as a line in the next report.
- Approval of non-budgeted spend — the team does not execute it until you confirm.
Operational questions
Three operational details that don’t fit inside the five objections.
On /preguntas-frecuentes we cover the five most common objections (price, software, onboarding, confidentiality, vs. VA). Here we answer the questions that come up once you’re already thinking about how to run the operation.
Keep reading
Four pages that complete the tour.
How we work answers “what happens once we sign.” The four pages below cover pricing, packages, downloadable resources, and FAQ — so you arrive at the audit with the full picture.
Plans & pricing
Three tiers: initial audit, monthly operations with a fixed team, or a single assigned coordinator.
See pricingPackages
Starter begins with a limited Founding Partner pilot and then continues at its standard monthly price; Growth is monthly operations, and Executive adds an assigned coordinator.
See packagesResources
Estimating template, standard work order, change-order checklist, and a calculator.
See resourcesFAQ
Difference vs. a traditional VA, price, software, onboarding, and confidentiality — with numbers.
See FAQNext step
Request your Operational Audit.
Five to seven business days to review your portfolio, your CRM, your templates, and the bottlenecks eating your hours. At the end, a clear report and an estimated number of hours recovered per month — no long-term contract to start.
Request an Operational AuditWe reply during U.S. Eastern business hours.