Agree the plan. Build in phases.
Start with a no-charge call. Before each phase, we agree what you get, the price and the schedule.
Packages
Start with a package
Four packages, each with its price on the page. Pick one and buy it online.
$199/month
Billed monthly
$182.42/month
Billed yearly
$499/month
Billed monthly
$457.42/month
Billed yearly
- Scammers stopped from sending email as you
- Your website and systems scanned every week
- Your email settings checked every week
- Everything in the 1 to 10 plan
- Covers up to 50 people
$199/month
after a one-time setup fee
- A site planned, designed and built for you
- Hosting and updates every month
$499/month
Billed monthly
$457.42/month
Billed yearly
$999/month
Billed monthly
$915.75/month
Billed yearly
- Your Google profile, fully set up
- A Google post every week
- 2 social posts a week
- Everything in Get found
- 4 social posts a week
- Your top 10 Google searches tracked
from$500/month
after a one-time setup fee
- Your data gathered from the tools you use
- A first analysis that answers your questions
- New findings every month
Onshore
US engineers, Central time
Senior engineers
Scope it, then build it
Proven on site
Before any rollout
Price agreed
Before each phase
What happens, in order.
Each phase is agreed separately.
Phase 1
First call
45 minutes · no charge
What breaks today, what that is costing you, and which of our teams would fix it.
What happens, what you get and how to leave
We discuss your current process, the problem, your goals and any deadlines or constraints. You leave with a recommendation and, if discovery is useful, a fixed-fee proposal.
What happens
- Walk through the current process and where it fails
- Establish what a good outcome would be worth
- Identify hard constraints: compliance, deadlines, existing vendors
- Agree whether discovery is justified
What you get
- A direct recommendation on the next step
- A discovery proposal with a fixed fee, if it’s warranted
ExitYou leave with a recommendation. There is nothing to cancel.
Phase 2
Discovery
1–4 weeks typical · fixed fee
Study the physical task, operating conditions, interfaces and feasibility.
What happens, what you get and how to leave
We inspect the task and site constraints, compare suitable components and identify the highest-risk assumptions. The plan defines the pilot, acceptance tests, cost and schedule.
What happens
- Study the task and operating environment
- Select sensors, actuators and controllers
- Map power, network and software interfaces
- Define pilot acceptance tests
What you get
- Feasibility and automation plan
- Proposed components and interfaces
- Pilot scope, estimate and risk register
ExitA fixed-fee engagement with a defined end. Continuing is a separate decision.
Phase 3
Pilot build
4–6 weeks typical · scope dependent
Build one working system and test it on site before rollout.
What happens, what you get and how to leave
We integrate the components, write the control software and test the pilot against the agreed task. Site testing establishes what needs to change before more units are deployed.
What happens
- Integrate components and control software
- Connect to the agreed systems
- Test the pilot in its operating environment
What you get
- A working pilot
- Documented test results
- Updated rollout plan
ExitThirty days’ notice after the first release, for any reason.
Phase 4
Refine and roll out
Ongoing, by agreement
Apply the pilot findings and deploy the agreed system.
What happens, what you get and how to leave
We revise the design using site-test results, document configuration and deploy the agreed units. Each rollout phase has its own scope and acceptance checks.
What happens
- Resolve findings from the pilot
- Prepare installation and configuration records
- Deploy and verify the agreed units
What you get
- Tested installations
- Configuration and operating documentation
- A handover and support plan
ExitMonth to month. No minimum term after the first release.
Phase 5
Maintenance & support
Ongoing, for as long as you want it
We keep the installed units running, and your team can take them over whenever you’d rather run them yourselves.
What happens, what you get and how to leave
Ongoing support can include control-software updates, calibration checks, fault diagnosis and small changes. We agree the coverage and response window. Design files, programs and records allow your team to take over.
What happens
- Control-software and firmware updates through the agreed update process
- Calibration checks against each sensor’s calibration record
- Fault diagnosis and repair within an agreed window
- A spares list kept current as parts change
- Transfer of design files, programs and configuration records whenever you ask
What you get
- A named support contact and an agreed response window
- Design files, programs and configuration records, kept current
- A spares list and a calibration record for every unit
ExitNo minimum term. Thirty days’ notice, for any reason. Every account is already in your name, and your data is returned and then destroyed as the Leaving terms set out.
Choose how we work together.
Fixed-fee discovery
Starting anything meaningful
- 1–4 weeks, depending on how much estate there is to map
- Fixed and agreed in advance, against your budget and requirements
- Deliverables defined in the engagement agreement
- No obligation to continue
Dedicated team
Sustained delivery against a roadmap
- Monthly, after the first release
- Named individuals, not a resource pool
- Thirty days’ notice, any reason
- Scale up or down at month boundaries
Outcome-based project
Well-specified scope with a hard date
- Fixed price against a defined scope
- Milestone-based payment
- Change control by written agreement
- Only offered post-discovery
Embedded engineers
Reinforcing a capable in-house team
- Monthly per engineer
- Your backlog, your ceremonies
- Our review and standards behind them
- Thirty days’ notice
We don’t bill by the hour
Discovery has a fixed fee. Delivery is priced as a monthly team or a defined outcome. The scope, fee and change process are agreed before each phase starts.
After launch, on purpose
After launch, you can retain a delivery team, agree a support arrangement or bring the work in-house. We set reliability targets for the system and plan the handover in advance.
How we estimate the work.
See the steps and what the estimate contains
Estimate slices, not features
A feature list contains no delivery risk, so estimating one produces a number that cannot be wrong until it is very wrong. We break the work into slices that are each independently deliverable, and estimate those. It is slower, and it is the reason a range narrows as the project proceeds instead of quietly widening.
Give a range, and say what sits at each end
You get a low and a high, plus the specific conditions that put the work at either end, not a single number with a padding factor buried in it. If we cannot describe what would have to be true for the top of the range, we do not understand the work well enough to have estimated it.
Write our assumptions as your obligations, with dates
Every estimate rests on things we assume about your side: an environment exists, someone can approve, a system has a test instance, a vendor answers. Those are listed as dated obligations in the statement of work rather than left implicit, because an unstated assumption is how a contractor manufactures a change order and calls it your fault.
Attach a confidence, and say what would raise it
Ranges carry a confidence level and the reason it is not higher. Usually the answer is one unknown that can be resolved by building something small, which is why discovery includes a spike against the single riskiest assumption rather than a longer document.
Agree who pays for a miss before the work starts
Modest variance is ours to absorb; that is the normal play in any estimate. A large miss means the estimate was a guess dressed as an estimate, which is our failure and not a change in your scope. The threshold between those two is a number in the statement of work, agreed before anyone starts, not a conversation in week nine.
Show the last estimate against what it actually cost
At every phase boundary you get the previous estimate next to the actual, and an explanation of any gap. This is the part firms leave out, and it is the only one that makes the rest verifiable: a method you cannot audit is a claim about our character, and you have no reason to take our word for that yet.
What the estimate contains
- A low and a high figure, with the conditions that produce each
- The slices behind them, priced individually
- Our assumptions restated as dated obligations on your side
- A confidence level, and the one unknown that would most improve it
- The overrun threshold and who carries each side of it
- Enough detail that another firm could price the same scope from it
Terms to review before work starts.
Ownership and licensing, Acceptance and payment, Scope and change, People, Data and security, Leaving
Ownership and licensing
“Work made for hire” is a copyright concept. It says nothing about patents or trade secrets, and it does not reach work done by a contractor, which is why the mechanism matters more than the label.
- Ownership and licensing settled in writing in the engagement agreement, before any work starts
- Whatever is agreed is agreed by express assignment rather than by relying on work-made-for-hire language
- Every engineer and subcontractor under written assignment before they touch the codebase, so there is a clean chain of title to assign
- Any third-party or open-source component identified, with its license and any fee attached
- No feedback clause. What you tell us about your business stays yours
Acceptance and payment
Acceptance testing is the protection most services contracts leave out, and the one that decides what happens when a deliverable is not what you asked for.
- Objective acceptance criteria written into the statement of work, not decided afterward
- Nothing is “deemed accepted” because time passed
- Rework to meet the agreed criteria is at our cost, inside a defined window
- On a fixed-scope phase, payment tied to milestones and acceptance rather than to the calendar
- Invoices are net 30, paid by purchase card, ACH or purchase order
- A holdback on each phase: a share of the fee we don’t invoice until you accept that phase
Scope and change
Underbidding a project and recovering the difference through change orders is a known pattern. The defense is a specific scope and a change process you control.
- A statement of work in active voice, naming who does what and by when
- Our assumptions rewritten as your obligations, with dates, so neither side discovers them late
- Every change priced and signed before the work starts
- Estimates given as a range with the assumptions stated, and a shared overrun mechanism agreed in advance
- No legal terms buried in a statement of work
People
The named team on the proposal and the team that arrives are frequently different. Staff turnover is the most reliable predictor of cost and delay on a long engagement.
- Key personnel named in the statement of work and not substituted without your consent
- Interview anyone you want to before they start
- You can require removal of anyone, for any lawful reason
- No charge for the ramp-up time of a replacement we initiated
- All delivery performed in the United States. Nothing subcontracted offshore
Data and security
Most privacy law holds you responsible for a breach whether it was your fault or your vendor’s. The contract is where that gets allocated.
- A security requirements exhibit specific to your data, not a pointer to our then-current policy
- Written notice of any actual or suspected incident within 24 hours
- You control the content, timing and method of any notification to your customers or regulators
- Log files and forensic cooperation preserved and provided
- A signed BAA where PHI is involved, and joint security testing where you want it
Leaving
The cost of leaving is set on the day you sign, not on the day you go.
- Termination for convenience on thirty days’ notice after the first release, no fee
- A hand-off phase in the plan from the start, not negotiated under pressure at the end
- Your data returned in a platform-neutral format as well as ours, then certified destroyed to NIST SP 800-88
- Documentation, runbooks and architecture decision records written as the work happens
- A named handover contact for a defined window after the last day, so the last question does not go unanswered
Cost, timing and project questions.
Yes, and it is usually the fastest way to get a useful answer: several of the pieces we publish end by asking for exactly that. Two things worth knowing first. This is an ordinary web form: it is encrypted in transit and the message lands in our mailbox and our own console, but it is not a secure document channel, so redact freely. A workbook with the numbers changed, a clause with the parties removed, a day of messages with the identifiers swapped: each of those answers the question as well as the original does, and we would rather read a redacted one. And if you would rather have an agreement in place before you send anything, say so in a line: we work under your paper rather than asking you to work under ours, and we redline rather than refuse.
Hardware work starts with a fixed-fee feasibility study and automation plan, agreed in advance, which can end in a recommendation not to build. The pilot build and each rollout phase are then quoted against a written scope, with acceptance tests, before that phase starts. Tell us the budget you have on the first call and we will tell you what is achievable inside it.
On résumé, they are ahead, and you should discount anyone who tells you otherwise. There are onshore firms in this space that have been doing it for eighteen, thirty, even fifty years, with senior engineers and named clients in your industry. The difference we would ask you to weigh is structural rather than technical. Most firms our competitors’ size specialize in one layer and subcontract or decline the rest, so the seams between the control network, the application, the estate and the security review end up owned by whoever is left in the room. We run those as four divisions inside one company, under one contract, which is why the escalation path ends somewhere useful instead of at a vendor boundary. That is the trade on offer: longer history and more logos on one side, and on the other a smaller senior team that can follow the problem across every layer it touches.
Yes. Your engineers contribute business knowledge and review the work with ours. Shared development and documentation also prepare your team for handover.
Thirty days’ notice after the first release, for any reason, with no termination fee. What you take with you when you go is settled in the engagement agreement before any work starts, and the hand-off phase is in the plan from the beginning rather than negotiated on the way out. We’d rather you were able to leave easily and chose not to.
Yes. We work under client paper rather than asking you to work under ours, and we redline rather than refuse. Security is handled through an exhibit written for your data rather than a pointer to our own policy, and the terms we will agree to there include notification of any actual or suspected incident within 24 hours, the content and timing of any notification to your customers or regulators left entirely in your control, a BAA where PHI is involved, and support for joint security testing. Questionnaires are part of onboarding rather than an afterthought. Send the requirements early, including whatever insurance you require us to carry, and we’ll flag anything we can’t meet.
Usually one of three ways, and we will tell you which is fastest for your institution rather than the one that suits us. First, subcontracting: we work under a prime who already holds the vehicle, which is the most common route for a firm at our stage and needs nothing new from your procurement office. Second, your own delegated authority: many institutions can issue a purchase order directly for services under their own limit, and those limits are set locally rather than centrally, so the number is yours to confirm. Third, a cooperative or state vehicle you already use. Being plain about that third one: we hold no cooperative or state contract awards today. Awards on those come through competitive solicitation cycles rather than on request, they are published, and any vendor implying otherwise is worth checking. If a vehicle is the only viable path for you, the honest answer is that we are the wrong firm this fiscal year, and we will say so on the first call rather than in month two.
All in the United States, all in Central time. We don’t subcontract delivery offshore. If a role requires clearance, citizenship or on-site presence, tell us early and we’ll be direct about whether we can staff it.
In the engagement agreement, in writing, before any work starts. Ownership and licensing are commercial terms rather than something we publish a standard answer to here, and they are settled with you during scoping. What we will say in general is that we do not rely on “work made for hire” language to do it: work for hire is a copyright doctrine that does not reach patents or trade secrets, and it reaches commissioned work only in nine narrow statutory categories that software is not one of, so whatever is agreed is agreed by express assignment. Any third-party or open-source component we use is listed with its license.
Acceptance criteria go in the statement of work, in objective terms, before the work starts. If something doesn’t meet them we fix it at our cost inside a defined window. Nothing is ever deemed accepted because time passed, and a holdback on each phase is released only on acceptance of that phase. If we can’t get it right, you stop paying for it.
Every change is priced and signed before work on it starts. We also rewrite our own assumptions as your obligations with dates attached, because an unstated assumption is how a contractor creates an exit and a change-order revenue stream at the same time. On estimated work we agree an overrun mechanism up front: modest variance is ours to absorb as the normal play in an estimate, and a large miss means the estimate was a guess, which is our problem rather than yours.
Mutual, with carve-outs that sit outside the cap: IP infringement indemnity, gross negligence, willful misconduct, and deliberate misuse of your confidential information. A cap that swallows the indemnity makes the indemnity decorative. We draw one line deliberately: a confidentiality breach we caused on purpose is uncapped, and one caused by a mistake sits under the cap or under a higher security-specific cap we will agree. We would rather set a cap we can actually fund than promise an unlimited number that nothing funds. We’ll negotiate it against the size and criticality of the engagement, and we’d rather have that conversation on the first call than in week six.
Whatever the engagement agreement says, and it says it before any work starts rather than at the end. Ownership, licensing and where the code and infrastructure are held are settled in writing during scoping, which is also what decides whether an escrow arrangement is worth anything to you. What does not depend on that negotiation: the hand-off phase is in the plan from the start rather than improvised under pressure, your data is exported in a platform-neutral format as well as ours and then certified destroyed to NIST SP 800-88, documentation, runbooks and architecture decision records are written as the work happens rather than assembled at the end, and there is a named handover contact for a defined window after the last day.
Next step
Tell us what’s breaking.
Forty-five minutes, no charge. We’ll say what we’d do, what it would likely cost, and whether the problem is in the hardware at all.
- Phone
- (214) 723-2510
- Reply
- A person replies, not a sequence: within one business day, from someone who would be on the engagement.
