All docs

How sync works

What moves between your CRM, Skematic and AWS Partner Central (ACE), in which direction, and how quickly.

The model: Skematic in the middle

Skematic sits between your CRM and ACE. Each of your deals becomes one Skematic opportunity, which is linked to its deal in the CRM and, once it's been sent, to its opportunity in ACE.

DirectionWhat movesHow
CRM → SkematicYour deals, with their company, contact, stage, value and datesAutomatically
Skematic → ACENew opportunities, submissions for AWS review, and updatesOnly when a person approves
ACE → SkematicAWS's review status and comments, stage changes, and new referrals from AWSAutomatically
Skematic → CRMACE's status on each deal (see ACE status in your CRM)Automatically

Skematic never deletes anything in your CRM or in ACE, and never changes your CRM's companies or contacts. The one exception is creating the deal and company for an AWS referral you accept.

Who owns each field

Each piece of information has one home, so the systems never fight over it.

InformationOwned byWhat that means
Customer company, address and contactYour CRMFix it in your CRM; Skematic reads it from there
Deal title, business problem, close date, deal type, industryYour CRM, unless changed in SkematicFollows your CRM until someone sets it in Skematic; then Skematic's value is used for ACE
StageYour CRM, unless set in SkematicTranslated to ACE's stages through Skematic's stage mapping
Co-sell details: use case, delivery model, sales activities, what you need from AWS, expected AWS spend, solution, and the other ACE fields your CRM doesn't holdSkematicYour CRM has no place for them, so Skematic drafts them or you set them in Skematic
Review status, AWS's comments, ACE opportunity IDACEDecided by AWS; Skematic reads them and shows them on your deal

When things happen

You don't need to press sync. Skematic picks changes up on its own:

ChangeReaches the other side
A deal created or edited in HubSpotUsually within a minute or two
A change in ACE (AWS's review, a stage change, a new referral)Usually within a minute, on your HubSpot deal too
Anything missed (an outage, a paused connection), or a deal moved to another companyAt the next regular check, every 15 minutes

A burst of changes is handled as one sync, so editing many deals at once is fine. Changes in your CRM don't travel on to ACE by themselves: updating ACE stays a person's decision (below).

Note: Quick updates from ACE need your AWS connection on the latest setup template. If Skematic shows your AWS connection as needing an update, apply it in your AWS account: Update AWS connection names the AWS account and region to sign into (if AWS says the stack does not exist, you're signed into another account or region). Until then, ACE changes arrive at the regular check.

What stays a person's decision

Skematic does the reading, matching and checking for you. Sending to AWS stays with your team:

  • Creating an opportunity in ACE, submitting it for AWS review, and updating it after AWS asks for changes.
  • Accepting or declining an AWS referral.
  • Approving Skematic's proposals: the fields it drafts, and stronger wording for opportunities already in ACE. They wait in your Inbox.

Each of these happens only when someone on your team asks for it: in Skematic, through an AI assistant connected to Skematic, or with an API key, always acting as that person. Each shows a preview first: exactly what AWS will receive or what will change. Skematic's own assistant asks you to approve every change before it's made. Only people who can make changes in your organization can do these; people with view-only access can see everything but change nothing. Every change is recorded, with who made it and how.

What Skematic does on its own: it reads your CRM and ACE, writes ACE's status onto your deals, creates the HubSpot deal for a referral you accepted in Partner Central, and asks AWS's Partner Central agent how your opportunities in ACE could be stronger. That question changes nothing in ACE.