Get clear on the work ahead.
The starting point, the team, the price, and what happens after delivery. Here are the questions founders ask before working with us.
Getting started
Founders of growing agencies and service businesses who need their sales, onboarding, and delivery systems to work together. You can bring one recurring workflow or an ongoing backlog.
Founders of growing agencies and service businesses who need their sales, onboarding, and delivery systems to work together. You can bring one recurring workflow or an ongoing backlog.
Founders of growing agencies and service businesses who need their sales, onboarding, and delivery systems to work together. You can bring one recurring workflow or an ongoing backlog.
Bring the problem and the tools involved. The initial conversation helps identify a practical first step and the information needed to scope it.
Bring the problem and the tools involved. The initial conversation helps identify a practical first step and the information needed to scope it.
Bring the problem and the tools involved. The initial conversation helps identify a practical first step and the information needed to scope it.
Yes. Automation Pilot starts from US$2,500 for one defined workflow. • One main trigger, up to three connected apps and up to eight agreed functional steps. • A Senior RevOps Engineer builds, tests and documents the workflow, then provides a walkthrough. • Standard delivery: 10–15 business days from kickoff and agreed access. Your delivery date is confirmed before you commit. We confirm tools, exceptions, acceptance tests and price before starting. More complex builds receive their own scope. Your paid Pilot includes a focused review of the related operation and a prioritized backlog at no additional cost.
Yes. Automation Pilot starts from US$2,500 for one defined workflow. • One main trigger, up to three connected apps and up to eight agreed functional steps. • A Senior RevOps Engineer builds, tests and documents the workflow, then provides a walkthrough. • Standard delivery: 10–15 business days from kickoff and agreed access. Your delivery date is confirmed before you commit. We confirm tools, exceptions, acceptance tests and price before starting. More complex builds receive their own scope. Your paid Pilot includes a focused review of the related operation and a prioritized backlog at no additional cost.
Yes. Automation Pilot starts from US$2,500 for one defined workflow. • One main trigger, up to three connected apps and up to eight agreed functional steps. • A Senior RevOps Engineer builds, tests and documents the workflow, then provides a walkthrough. • Standard delivery: 10–15 business days from kickoff and agreed access. Your delivery date is confirmed before you commit. We confirm tools, exceptions, acceptance tests and price before starting. More complex builds receive their own scope. Your paid Pilot includes a focused review of the related operation and a prioritized backlog at no additional cost.
Yes. Your paid Pilot includes a focused review of the related operation and a prioritized backlog at no additional cost. • A focused session of up to 45 minutes. • Review of up to three related workflows. • Up to ten genuine automation opportunities, based on the work reviewed. Your Senior RevOps Engineer recommends priorities using the business problem, proposed build, expected impact, relative effort, dependencies and acceptance criteria. You validate business priorities; the Delivery Manager maintains the client relationship and backlog traceability. Use the backlog with your own team, another provider or our Squad. Ongoing execution is a separate engagement. We include genuine opportunities rather than filling a quota.
Yes. Your paid Pilot includes a focused review of the related operation and a prioritized backlog at no additional cost. • A focused session of up to 45 minutes. • Review of up to three related workflows. • Up to ten genuine automation opportunities, based on the work reviewed. Your Senior RevOps Engineer recommends priorities using the business problem, proposed build, expected impact, relative effort, dependencies and acceptance criteria. You validate business priorities; the Delivery Manager maintains the client relationship and backlog traceability. Use the backlog with your own team, another provider or our Squad. Ongoing execution is a separate engagement. We include genuine opportunities rather than filling a quota.
Yes. Your paid Pilot includes a focused review of the related operation and a prioritized backlog at no additional cost. • A focused session of up to 45 minutes. • Review of up to three related workflows. • Up to ten genuine automation opportunities, based on the work reviewed. Your Senior RevOps Engineer recommends priorities using the business problem, proposed build, expected impact, relative effort, dependencies and acceptance criteria. You validate business priorities; the Delivery Manager maintains the client relationship and backlog traceability. Use the backlog with your own team, another provider or our Squad. Ongoing execution is a separate engagement. We include genuine opportunities rather than filling a quota.
Yes. If recurring needs are clear, you can start with the monthly team. We agree on priorities, capacity, responsibilities, and support before starting.
Yes. If recurring needs are clear, you can start with the monthly team. We agree on priorities, capacity, responsibilities, and support before starting.
Yes. If recurring needs are clear, you can start with the monthly team. We agree on priorities, capacity, responsibilities, and support before starting.
Monthly work
Monthly team capacity • RevOps Builder Squad: 58 hours — 45 development, 5 solution design and 8 delivery management. • AI Engineering Partner: 68 hours — 60 development hours shared by the AI Engineering Lead and Full-Stack Developer, plus 8 delivery management. • Strategic Operations Partner: 74 hours — 45 development, 5 solution design, 16 senior operations and 8 delivery management. Each plan has one main active workstream. Priorities, completion criteria and milestones are agreed around the available capacity. Development includes implementation, testing, documentation and handoff. AI development also includes evaluation and iteration. Additional work can be reprioritized or receive agreed additional capacity.
Monthly team capacity • RevOps Builder Squad: 58 hours — 45 development, 5 solution design and 8 delivery management. • AI Engineering Partner: 68 hours — 60 development hours shared by the AI Engineering Lead and Full-Stack Developer, plus 8 delivery management. • Strategic Operations Partner: 74 hours — 45 development, 5 solution design, 16 senior operations and 8 delivery management. Each plan has one main active workstream. Priorities, completion criteria and milestones are agreed around the available capacity. Development includes implementation, testing, documentation and handoff. AI development also includes evaluation and iteration. Additional work can be reprioritized or receive agreed additional capacity.
Monthly team capacity • RevOps Builder Squad: 58 hours — 45 development, 5 solution design and 8 delivery management. • AI Engineering Partner: 68 hours — 60 development hours shared by the AI Engineering Lead and Full-Stack Developer, plus 8 delivery management. • Strategic Operations Partner: 74 hours — 45 development, 5 solution design, 16 senior operations and 8 delivery management. Each plan has one main active workstream. Priorities, completion criteria and milestones are agreed around the available capacity. Development includes implementation, testing, documentation and handoff. AI development also includes evaluation and iteration. Additional work can be reprioritized or receive agreed additional capacity.
The Squad is a managed monthly engagement around a prioritized backlog and an agreed delivery plan. Its 58 team hours/month define reserved capacity: 45 development, 5 solution design and 8 delivery management. Your Delivery Manager coordinates the work; the technical team estimates and delivers it. Capacity is tracked transparently, and additional capacity is agreed before work starts.
The Squad is a managed monthly engagement around a prioritized backlog and an agreed delivery plan. Its 58 team hours/month define reserved capacity: 45 development, 5 solution design and 8 delivery management. Your Delivery Manager coordinates the work; the technical team estimates and delivers it. Capacity is tracked transparently, and additional capacity is agreed before work starts.
The Squad is a managed monthly engagement around a prioritized backlog and an agreed delivery plan. Its 58 team hours/month define reserved capacity: 45 development, 5 solution design and 8 delivery management. Your Delivery Manager coordinates the work; the technical team estimates and delivers it. Capacity is tracked transparently, and additional capacity is agreed before work starts.
Three-month initial engagement, billed monthly. • At the starting rate: US$13,500 across three monthly invoices, subject to First-Milestone Protection. • One main active workstream, a weekly 30-minute review and async updates. • At the starting US$4,500/month rate, the team provides 58 monthly team hours: 45 development + 5 solution design + 8 delivery management. • Your proposal confirms the final fee, allocation and support. • We agree on a material first milestone within your first 30 days. • If a miss caused by Techmark is not corrected within 10 business days of the milestone date, you can end the remaining initial commitment without an exit fee. • Future-month billing is paused during the correction period. • The first month and authorized third-party costs remain payable.
Three-month initial engagement, billed monthly. • At the starting rate: US$13,500 across three monthly invoices, subject to First-Milestone Protection. • One main active workstream, a weekly 30-minute review and async updates. • At the starting US$4,500/month rate, the team provides 58 monthly team hours: 45 development + 5 solution design + 8 delivery management. • Your proposal confirms the final fee, allocation and support. • We agree on a material first milestone within your first 30 days. • If a miss caused by Techmark is not corrected within 10 business days of the milestone date, you can end the remaining initial commitment without an exit fee. • Future-month billing is paused during the correction period. • The first month and authorized third-party costs remain payable.
Three-month initial engagement, billed monthly. • At the starting rate: US$13,500 across three monthly invoices, subject to First-Milestone Protection. • One main active workstream, a weekly 30-minute review and async updates. • At the starting US$4,500/month rate, the team provides 58 monthly team hours: 45 development + 5 solution design + 8 delivery management. • Your proposal confirms the final fee, allocation and support. • We agree on a material first milestone within your first 30 days. • If a miss caused by Techmark is not corrected within 10 business days of the milestone date, you can end the remaining initial commitment without an exit fee. • Future-month billing is paused during the correction period. • The first month and authorized third-party costs remain payable.
RevOps Builder Squad • Recurring CRM, automation, reporting and integration priorities. • 58 team hours/month: 45 development, 5 solution design and 8 delivery management. AI Engineering Partner • One AI use case needing ongoing development, evaluation and iteration. • 68 team hours/month: 60 development hours shared by the AI Engineering Lead and Full-Stack Developer, plus 8 delivery management. The AI Engineering Lead contributes to the build and owns technical direction. The split between the two engineers follows the agreed work.
RevOps Builder Squad • Recurring CRM, automation, reporting and integration priorities. • 58 team hours/month: 45 development, 5 solution design and 8 delivery management. AI Engineering Partner • One AI use case needing ongoing development, evaluation and iteration. • 68 team hours/month: 60 development hours shared by the AI Engineering Lead and Full-Stack Developer, plus 8 delivery management. The AI Engineering Lead contributes to the build and owns technical direction. The split between the two engineers follows the agreed work.
RevOps Builder Squad • Recurring CRM, automation, reporting and integration priorities. • 58 team hours/month: 45 development, 5 solution design and 8 delivery management. AI Engineering Partner • One AI use case needing ongoing development, evaluation and iteration. • 68 team hours/month: 60 development hours shared by the AI Engineering Lead and Full-Stack Developer, plus 8 delivery management. The AI Engineering Lead contributes to the build and owns technical direction. The split between the two engineers follows the agreed work.
It adds 16 Senior Operations Manager hours to the 58-hour Squad, for 74 team hours/month. • 45 development + 5 solution design hours. • 16 senior operations + 8 delivery management hours. The Senior Operations Manager directs the roadmap and aligns process owners, priorities and indicators. The Delivery Manager coordinates delivery, dependencies, decisions and progress. Strategic Operations Partner includes the Squad. AI Engineering Partner is a separate engagement.
It adds 16 Senior Operations Manager hours to the 58-hour Squad, for 74 team hours/month. • 45 development + 5 solution design hours. • 16 senior operations + 8 delivery management hours. The Senior Operations Manager directs the roadmap and aligns process owners, priorities and indicators. The Delivery Manager coordinates delivery, dependencies, decisions and progress. Strategic Operations Partner includes the Squad. AI Engineering Partner is a separate engagement.
It adds 16 Senior Operations Manager hours to the 58-hour Squad, for 74 team hours/month. • 45 development + 5 solution design hours. • 16 senior operations + 8 delivery management hours. The Senior Operations Manager directs the roadmap and aligns process owners, priorities and indicators. The Delivery Manager coordinates delivery, dependencies, decisions and progress. Strategic Operations Partner includes the Squad. AI Engineering Partner is a separate engagement.
They are included in the monthly fee and counted separately from development, solution design and senior operations. • Organizing the backlog, briefs and owners. • Coordinating dependencies and following up on decisions. • Progress updates and the agreed review cadence. The Delivery Manager’s time in meetings counts within these 8 hours. Engineers and the Senior Operations Manager record their meeting time against their own allocations. You approve business priorities and decisions.
They are included in the monthly fee and counted separately from development, solution design and senior operations. • Organizing the backlog, briefs and owners. • Coordinating dependencies and following up on decisions. • Progress updates and the agreed review cadence. The Delivery Manager’s time in meetings counts within these 8 hours. Engineers and the Senior Operations Manager record their meeting time against their own allocations. You approve business priorities and decisions.
They are included in the monthly fee and counted separately from development, solution design and senior operations. • Organizing the backlog, briefs and owners. • Coordinating dependencies and following up on decisions. • Progress updates and the agreed review cadence. The Delivery Manager’s time in meetings counts within these 8 hours. Engineers and the Senior Operations Manager record their meeting time against their own allocations. You approve business priorities and decisions.
Team hours combine the time contributed by the assigned professionals. For example, a one-hour session with two team members uses two team hours, recorded against their respective allocations. Your monthly plan shows the work, people involved and capacity used. Multiple roles do not imply full-time or exclusive staffing.
Team hours combine the time contributed by the assigned professionals. For example, a one-hour session with two team members uses two team hours, recorded against their respective allocations. Your monthly plan shows the work, people involved and capacity used. Multiple roles do not imply full-time or exclusive staffing.
Team hours combine the time contributed by the assigned professionals. For example, a one-hour session with two team members uses two team hours, recorded against their respective allocations. Your monthly plan shows the work, people involved and capacity used. Multiple roles do not imply full-time or exclusive staffing.
Delivery
Standard Pilot: 10–15 business days from kickoff and agreed access. Your delivery date is confirmed before you commit. The start date depends on actual capacity and is confirmed before contracting.
Standard Pilot: 10–15 business days from kickoff and agreed access. Your delivery date is confirmed before you commit. The start date depends on actual capacity and is confirmed before contracting.
Standard Pilot: 10–15 business days from kickoff and agreed access. Your delivery date is confirmed before you commit. The start date depends on actual capacity and is confirmed before contracting.
For a standard Pilot, plan for about 2–3 hours across kickoff, the focused audit and review or handoff, plus access and internal approvals. • Your Senior RevOps Engineer owns the technical build and backlog recommendations. • Your Delivery Manager coordinates reviews and maintains the client relationship and agreed priorities.
For a standard Pilot, plan for about 2–3 hours across kickoff, the focused audit and review or handoff, plus access and internal approvals. • Your Senior RevOps Engineer owns the technical build and backlog recommendations. • Your Delivery Manager coordinates reviews and maintains the client relationship and agreed priorities.
For a standard Pilot, plan for about 2–3 hours across kickoff, the focused audit and review or handoff, plus access and internal approvals. • Your Senior RevOps Engineer owns the technical build and backlog recommendations. • Your Delivery Manager coordinates reviews and maintains the client relationship and agreed priorities.
Continuity & privacy
Monthly support is optional after a project. You can scope the next build separately, arrange System Care for a delivered system, or choose a monthly team for recurring improvements.
Monthly support is optional after a project. You can scope the next build separately, arrange System Care for a delivered system, or choose a monthly team for recurring improvements.
Monthly support is optional after a project. You can scope the next build separately, arrange System Care for a delivered system, or choose a monthly team for recurring improvements.
We work in your accounts where practical and hand over documentation and exportable configuration where the tools support it. Your audit and backlog stay with you. Choose the support you need after delivery. Ownership of custom work, reusable components and third-party licenses remains defined in the proposal.
We work in your accounts where practical and hand over documentation and exportable configuration where the tools support it. Your audit and backlog stay with you. Choose the support you need after delivery. Ownership of custom work, reusable components and third-party licenses remains defined in the proposal.
We work in your accounts where practical and hand over documentation and exportable configuration where the tools support it. Your audit and backlog stay with you. Choose the support you need after delivery. Ownership of custom work, reusable components and third-party licenses remains defined in the proposal.
Software subscriptions, hosting and AI/API usage are paid by the client and are separate from Techmark’s service fees. Your proposal identifies the relevant vendor costs and support terms.
Software subscriptions, hosting and AI/API usage are paid by the client and are separate from Techmark’s service fees. Your proposal identifies the relevant vendor costs and support terms.
Software subscriptions, hosting and AI/API usage are paid by the client and are separate from Techmark’s service fees. Your proposal identifies the relevant vendor costs and support terms.
We sign an NDA before starting work or accessing your systems. • Access and responsibilities are agreed around the scope of the engagement.
We sign an NDA before starting work or accessing your systems. • Access and responsibilities are agreed around the scope of the engagement.
We sign an NDA before starting work or accessing your systems. • Access and responsibilities are agreed around the scope of the engagement.
Before starting, we agree on the workflow, material acceptance criteria, delivery date and required inputs. • If a delivery failure caused by Techmark prevents the agreed criteria from being met, we have 10 business days after the agreed delivery date to correct it at no additional implementation fee. • If the criteria remain unmet, you may request a refund of the full Pilot implementation fee you paid within 30 calendar days after the correction period ends. • We process a covered refund within 10 business days of receiving the request. • You keep the included audit and backlog. • Software subscriptions, hosting, AI/API usage and other third-party charges are excluded. • Scope changes, unavailable access, client decisions or external service failures adjust the plan only where they affect delivery, with the change documented. • The guarantee covers the agreed delivery, rather than a revenue or savings target.
Before starting, we agree on the workflow, material acceptance criteria, delivery date and required inputs. • If a delivery failure caused by Techmark prevents the agreed criteria from being met, we have 10 business days after the agreed delivery date to correct it at no additional implementation fee. • If the criteria remain unmet, you may request a refund of the full Pilot implementation fee you paid within 30 calendar days after the correction period ends. • We process a covered refund within 10 business days of receiving the request. • You keep the included audit and backlog. • Software subscriptions, hosting, AI/API usage and other third-party charges are excluded. • Scope changes, unavailable access, client decisions or external service failures adjust the plan only where they affect delivery, with the change documented. • The guarantee covers the agreed delivery, rather than a revenue or savings target.
Before starting, we agree on the workflow, material acceptance criteria, delivery date and required inputs. • If a delivery failure caused by Techmark prevents the agreed criteria from being met, we have 10 business days after the agreed delivery date to correct it at no additional implementation fee. • If the criteria remain unmet, you may request a refund of the full Pilot implementation fee you paid within 30 calendar days after the correction period ends. • We process a covered refund within 10 business days of receiving the request. • You keep the included audit and backlog. • Software subscriptions, hosting, AI/API usage and other third-party charges are excluded. • Scope changes, unavailable access, client decisions or external service failures adjust the plan only where they affect delivery, with the change documented. • The guarantee covers the agreed delivery, rather than a revenue or savings target.
At kickoff, we agree on a material first milestone, acceptance criteria and a date within the first 30 calendar days, with the required inputs available. • If Techmark misses it for a cause attributable to our team, we have 10 business days from the milestone date to correct it at no extra fee. • Future-month charges falling due during that correction period are paused. • If we still have not met the milestone, you may request to end the remaining initial commitment within 30 calendar days after the correction period, without an exit fee. • Any future months already charged but not started are refunded within 10 business days. • The first month is not refunded under this protection, and authorized third-party costs remain payable. • If the milestone is corrected, we agree the remaining billing schedule in writing. • This is a specific protection against first-milestone non-delivery, rather than general monthly cancellation.
At kickoff, we agree on a material first milestone, acceptance criteria and a date within the first 30 calendar days, with the required inputs available. • If Techmark misses it for a cause attributable to our team, we have 10 business days from the milestone date to correct it at no extra fee. • Future-month charges falling due during that correction period are paused. • If we still have not met the milestone, you may request to end the remaining initial commitment within 30 calendar days after the correction period, without an exit fee. • Any future months already charged but not started are refunded within 10 business days. • The first month is not refunded under this protection, and authorized third-party costs remain payable. • If the milestone is corrected, we agree the remaining billing schedule in writing. • This is a specific protection against first-milestone non-delivery, rather than general monthly cancellation.
At kickoff, we agree on a material first milestone, acceptance criteria and a date within the first 30 calendar days, with the required inputs available. • If Techmark misses it for a cause attributable to our team, we have 10 business days from the milestone date to correct it at no extra fee. • Future-month charges falling due during that correction period are paused. • If we still have not met the milestone, you may request to end the remaining initial commitment within 30 calendar days after the correction period, without an exit fee. • Any future months already charged but not started are refunded within 10 business days. • The first month is not refunded under this protection, and authorized third-party costs remain payable. • If the milestone is corrected, we agree the remaining billing schedule in writing. • This is a specific protection against first-milestone non-delivery, rather than general monthly cancellation.
One workflow with one main trigger, up to three connected apps and up to eight agreed functional steps, with a clear operational outcome. • Tools, exceptions, acceptance tests and price are confirmed before starting. • We assess usable APIs or integrations, functional steps, human review and exceptions. A complex operation needs assessment even when counted as one step. • Large migrations, new portals, multiple independent workflows and systems without usable access need their own scope. More complex builds receive a separate assessment.
One workflow with one main trigger, up to three connected apps and up to eight agreed functional steps, with a clear operational outcome. • Tools, exceptions, acceptance tests and price are confirmed before starting. • We assess usable APIs or integrations, functional steps, human review and exceptions. A complex operation needs assessment even when counted as one step. • Large migrations, new portals, multiple independent workflows and systems without usable access need their own scope. More complex builds receive a separate assessment.
One workflow with one main trigger, up to three connected apps and up to eight agreed functional steps, with a clear operational outcome. • Tools, exceptions, acceptance tests and price are confirmed before starting. • We assess usable APIs or integrations, functional steps, human review and exceptions. A complex operation needs assessment even when counted as one step. • Large migrations, new portals, multiple independent workflows and systems without usable access need their own scope. More complex builds receive a separate assessment.
For 30 calendar days after go-live, we correct reproducible bugs that stop the delivered workflow from behaving as accepted. • We acknowledge a report by the next business day. • New features, scope changes, later third-party changes and ongoing care are covered by a separate agreement. • We work in your accounts where practical and hand over documentation and exportable configuration where the tools support it. • Your audit and backlog stay with you. • Choose the support you need after delivery. • Third-party licenses and restrictions still apply. • System Care and Expert Support remain separate engagements.
For 30 calendar days after go-live, we correct reproducible bugs that stop the delivered workflow from behaving as accepted. • We acknowledge a report by the next business day. • New features, scope changes, later third-party changes and ongoing care are covered by a separate agreement. • We work in your accounts where practical and hand over documentation and exportable configuration where the tools support it. • Your audit and backlog stay with you. • Choose the support you need after delivery. • Third-party licenses and restrictions still apply. • System Care and Expert Support remain separate engagements.
For 30 calendar days after go-live, we correct reproducible bugs that stop the delivered workflow from behaving as accepted. • We acknowledge a report by the next business day. • New features, scope changes, later third-party changes and ongoing care are covered by a separate agreement. • We work in your accounts where practical and hand over documentation and exportable configuration where the tools support it. • Your audit and backlog stay with you. • Choose the support you need after delivery. • Third-party licenses and restrictions still apply. • System Care and Expert Support remain separate engagements.