ProgrammableMarketing/getauctor.com (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 6
  • This quarter · 13
  • Big bets · 3
  • Wildcards · 1
  • How we can help
Generated Nov 9, 2026 1 view
  1. Programmable
  2. Playbooks
  3. Auctor
Auctor logo

growth playbook · Nov 9, 2026

getauctor.com (opens in a new tab)

Auctor growth playbook

Diagnosis

Auctor raised $20 million led by Sequoia, has 14 implementation firms on its homepage (including NTT DATA, Myers-Holum, CoreX and Softype), and is hiring a Founding AE, a Customer Success Manager, a Deployment Strategist and six engineers in New York. Its buyers think in ecosystems: a NetSuite partner, a ServiceNow partner, an SAP practice.

The website doesn't. Its best ecosystem-specific copy sits on event pages whose dates have passed, the product page names no ecosystem, and 12 of 13 customer stories show no result. There is no marketing hire. This playbook first turns the event pages into permanent ecosystem pages and puts a number on every story.

Next it builds a sales and success engine around ROI reports, a sharper demo path, integration pages and "Auctor and your PSA" positioning. Then it bets on co-selling with its ecosystem investors, an annual scope-drift report and vendors' own services teams.

Growth Score

7/10

Biggest Opportunity

Sell by ecosystem: permanent NetSuite, ServiceNow, SAP, Workday and Salesforce pages with peer proof, so every conference, dinner and referral leaves a page that keeps selling.

Biggest Risk

Rocketlane and Kantata are adding AI agents to the PSA tools services firms already pay for, and general-purpose AI assistants look "good enough". Without measured, named results, Auctor's claims read like everyone else's.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Turn the expired SuiteWorld, SAP, Knowledge and Dreamforce pages into permanent ecosystem pages

    Draft /netsuite from the SuiteWorld page and the Softype, Bring IT and Myers-Holum stories, then redirect /auctor-suiteworld and /book-at-suiteworld to it.

    High impact First result in 3-6 weeks
  2. 2

    Put a named result on every customer story, starting with the four unattributed "By the numbers" figures

    List which customer and project each of the four "By the numbers" figures came from.

    High impact First result in 3 weeks
  3. 3

    Add a three-minute walkthrough to the demo page and every workflow page

    Record the "Your Discovery Call Writes Itself" walkthrough on a sample project.

    High impact First result in 2 weeks

02

Your idea portfolio

23 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 8 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 3Big bets · 10Fill-ins · 6Reconsider · 4
Effort →

Showing 23 of 23 ideas

This week 6

Quick wins with a clear first action.

  • 01

    Auctor sells to systems integrators, and SIs live inside one ecosystem: a NetSuite partner, a ServiceNow partner, an SAP practice. Auctor's most specific copy for each ecosystem sits on event pages whose dates have passed but which are still in the sitemap. "Meet us at SuiteWorld" (October 25–28) has "Auctor in the NetSuite ecosystem" with Bring IT, Myers Holum and Softype. The SAP webinar (October 7) covers margin lost before configuration. There is a ServiceNow Knowledge dinner page, three Workday Rising pages and three Dreamforce pages. Meanwhile the product page names none of NetSuite, Workday, SAP or ServiceNow, and the customers page can't be filtered by ecosystem. A NetSuite partner who heard about Auctor at the show and searches later lands on a booking page for a meeting that already happened.

    High impactMedium effort First result in 3-6 weeks Founder

    First action

    Draft /netsuite from the SuiteWorld page and the Softype, Bring IT and Myers-Holum stories, then redirect /auctor-suiteworld and /book-at-suiteworld to it.

    How to measure it

    Ecosystem-page demo requests

    Now
    –
    Target
    10 qualified demos a month
    By
    90 days

    Steps

    1. 1

      Map stories to ecosystems

      Tag all 13 customer stories and 14 logos by ecosystem; note which ecosystem has no story yet.

      Founder (go-to-market) 1 day

    2. 2

      Write the NetSuite page

      Reuse the SuiteWorld copy, Softype's numbers and the Bring IT and Myers-Holum stories.

      Founder (go-to-market) 2 days

    3. 3

      Write the SAP and ServiceNow pages

      SAP from the webinar and NTT DATA story; ServiceNow from the Knowledge dinner and CoreX.

      Founder (go-to-market) 3 days

    4. 4

      Add Workday and Salesforce

      Start from the Workday Rising and Dreamforce copy and the Salesforce integration; add a story as soon as one exists.

      Founder (go-to-market) 3 days

    5. 5

      Redirect event URLs

      301 the past event pages to the matching ecosystem page and update the sitemap.

      Software Engineer 1 day

    6. 6

      Tag the demo form

      Pass the ecosystem into the CRM so the AE opens with the right story.

      Founding Account Executive 1 day

    7. 7

      Link from the site

      Navigation, product page and a filter on the customers page.

      Software Engineer 1 day

    8. 8

      Measure

      Search impressions for ecosystem queries and demos by page, monthly.

      Founder (go-to-market) monthly

    First result
    3-6 weeks
    Cost
    About two weeks of founder and engineer time; no paid tools
    Owner
    Founder (go to market)

    Smallest test

    Publish /netsuite, redirect the two SuiteWorld URLs to it, and share it with every SuiteWorld contact.

    Why it works

    Build five permanent pages, /netsuite, /servicenow, /sap, /workday and /salesforce, from copy that already exists. Each page has: the ecosystem's own deliverables and pain (Fit-to-Standard decisions and change requests for SAP; RFP responses and discovery questions for NetSuite); the peer stories (NetSuite: Softype, Bring IT, Myers-Holum; SAP: NTT DATA; ServiceNow: CoreX); the integrations that matter; the "Bring us your hardest implementation problem" offer; and a demo form tagged with the ecosystem. 301-redirect each past event URL to its ecosystem page, keeping a small "Meet us at the next show" block. Then link all five from the navigation, the product page and the customers page. Upside: every conference, dinner and partner mention leaves a page that keeps ranking and converting. The Founding AE also gets one link per segment to send after a call.

    Implementation buyers trust peers in their own ecosystem more than general claims, and they search with the ecosystem name in the query. A permanent page collects the links and attention each event creates, instead of letting them go stale on a dated page.

    Ready to use

    ChecklistEcosystem page template

    [ ] H1: "Auctor for <ecosystem> partners"
    [ ] The three deliverables this ecosystem's partners produce most (e.g. Fit-to-Standard log, RFP response, user stories)
    [ ] One peer story with a number, plus logos of other partners in the ecosystem
    [ ] Integrations used in this ecosystem
    [ ] "Bring us your hardest <ecosystem> implementation problem" offer
    [ ] Demo form with the ecosystem preselected
    [ ] Next event block (replaces the dated event page)
    [ ] 301s from past event URLs, sitemap updated

    Risks and how to handle them

    • Thin pages for ecosystems with no customer story yet

      Launch NetSuite, SAP and ServiceNow first; add Workday and Salesforce when a story is ready.

    • Partners object to their name on a vendor page

      Use only stories they have already published with Auctor and send them the page before launch.

    Evidence

    • Your websiteEvent pages still live after the events: the SAP webinar "Where SAP Implementations Lose Margin Before Configuration Starts" (October 7, 2026; "The recording will be emailed to all registered participants"); "Meet us at SuiteWorld" (October 25–28, 2026), covering "Auctor in the NetSuite ecosystem" with Bring IT, Myers Holum and Softype and the offer "Bring us your hardest implementation problem"; a Dreamforce 5K on September 15; and "Full Context at Knowledge 26", an invitation-only dinner in ServiceNow's conference week on May 4, 2026, "third in the series, after Chicago and New York".Source
    • Your websiteSitemap (52 URLs, checked November 9, 2026): event pages for Workday Rising (three), Dreamforce (three), SuiteWorld (two), ServiceNow Knowledge 26 and an SAP webinar; two integration pages (/hubspot-integration, /slack-integration); customer stories and partner posts filed under /blog; six /workflow pages; no ecosystem, comparison, pricing, integrations-directory or changelog pages.Source
    • Your websiteProduct page: Capture, Contextualize, Create; features include "Proof of performance", "Trace every requirement", "Draft smarter with AI" (first drafts of SOWs, scopes and designs) and "Standardize every implementation"; 19 integrations listed, among them Salesforce, Gong, HubSpot, Certinia, Jira, Confluence, Azure DevOps, Linear, Rally, Slack, Microsoft Teams and Zoom; the page names none of NetSuite, Workday, SAP or ServiceNow.Source
    • Your websiteCustomers page: 13 stories (2 "Customer Stories", 11 "Case Studies"); only Softype shows a result in its summary ("$2-3M in pipeline"); the four "By the numbers" figures (90% less time getting up to speed, 70% faster story and requirements finalization, 10+ hours saved per person per week, 80% quicker artifact creation) are not tied to any customer; Valiantys appears twice (/blog/valiantys and /blog/valiantys-case-study); titles such as "CoreX and Auctor" and "NTT and Auctor" carry no outcome; there is no filter by ecosystem, although the stories span NetSuite, ServiceNow, Salesforce, Atlassian, OneStream and SAP.Source
    • HiringFounding Account Executive (New York, posted February 6, 2026): "Own the sales process from prospecting to close, targeting emerging, mid-market, and enterprise Systems Integrators", running discovery and demos for technical audiences without a Sales Engineer on every call; Auctor automates work that "powers $400B+ in services work".Source
  • 02

    The customers page shows 90% less ramp-up time, 70% faster requirements, 10+ hours saved per person per week and 80% quicker artifacts, but ties none of them to a customer. Of 13 stories, only Softype's summary has a number. The homepage has testimonials but no quantified results. Softype's story shows how strong a specific number is: RFPs cut from 2–3 weeks to 1–2 days, and $2–3M quoted.

    High impactLow effort First result in 3 weeks Customer Success Manager

    First action

    List which customer and project each of the four "By the numbers" figures came from.

    How to measure it

    Quantified stories

    Now
    –
    Target
    10 of 13
    By
    45 days

    Steps

    1. 1

      Source the four figures

      Find the customer and project behind each headline number.

      Customer Success Manager 2 days

    2. 2

      Pull usage numbers

      Artifacts generated, active users and time saved for each story account.

      Software Engineer 3 days

    3. 3

      Agree with customers

      One number per story, approved for publication.

      Customer Success Manager 2 weeks

    4. 4

      Rewrite cards

      Number in the headline and on the customers-page card.

      Founder (go-to-market) 2 days

    5. 5

      Add to the homepage

      Three named results under the logo row.

      Software Engineer 1 day

    6. 6

      Arm sales

      A one-page proof sheet by ecosystem.

      Founding Account Executive 1 day

    First result
    3 weeks
    Cost
    Staff time only
    Owner
    Customer Success Manager

    Smallest test

    Attribute one of the four headline figures this week and put it on the homepage.

    Why it works

    Trace each "By the numbers" figure back to the customer and project it came from, and get permission to name it ("80% quicker artifact creation at Ravus"). For every story without a figure, the Customer Success Manager pulls one usage-based number from the account (artifacts generated, hours saved on RFPs, team size versus project size) and confirms it with the customer. Put the number in each story's title or first line and on the customers page card.

    Services buyers sell on margin and utilization themselves, and they discount unattributed percentages. A named peer number is the proof the Founding AE can quote on a call.

    Risks and how to handle them

    • Customers won't approve numbers

      Offer a range or a relative figure, and credit their team for the result.

    Evidence

    • Your websiteCustomers page: 13 stories (2 "Customer Stories", 11 "Case Studies"); only Softype shows a result in its summary ("$2-3M in pipeline"); the four "By the numbers" figures (90% less time getting up to speed, 70% faster story and requirements finalization, 10+ hours saved per person per week, 80% quicker artifact creation) are not tied to any customer; Valiantys appears twice (/blog/valiantys and /blog/valiantys-case-study); titles such as "CoreX and Auctor" and "NTT and Auctor" carry no outcome; there is no filter by ecosystem, although the stories span NetSuite, ServiceNow, Salesforce, Atlassian, OneStream and SAP.Source
    • Your websiteSoftype case study (a NetSuite-only consultancy): "$2–3M in client opportunities quoted (YTD)"; RFP turnaround cut from "~2–3 weeks to 1–2 days"; RFP team from 2–3 people to 1; "About 40 discovery questions generated in 30 seconds"; the founder: "Having Auctor feels like having a few extra people working on these tasks with great ease and consistency."Source
    • Your websiteHomepage (checked November 9, 2026): H1 "One System, Every Implementation"; 14 customer logos including NTT DATA, Myers-Holum, CoreX, Bring IT, Softype, Valiantys and ServiceRocket; investor logos Sequoia, Y Combinator, M12, HubSpot Ventures, Workday Ventures and OneStream; four testimonials but no quantified results; "Book a Demo" is the only way in; no pricing.Source
    • HiringCustomer Success Manager (New York, posted September 14, 2026): "Manage onboarding, adoption, health checks, QBRs, and renewals" for "a portfolio of implementation partners and systems integrators", and "Build and present ROI narratives that connect Auctor usage (sessions, artifacts generated, active users) to real outcomes".Source
  • 03

    Several story titles say only "CoreX and Auctor", "NTT and Auctor" or "Valiantys and Auctor", so neither search results nor the cards say what happened. Valiantys has two separate pages. The footer link labelled "Case Studies" goes to /resources, not /customers. The homepage CoreX logo links to corexcorp.com, which returned 404 when checked.

    Medium impactLow effort First result in 2 weeks Founder

    First action

    Fix the footer "Case Studies" link and the CoreX logo link today.

    How to measure it

    Story click-through

    Now
    –
    Target
    +30%
    By
    60 days

    Steps

    1. 1

      Fix the two links

      Footer "Case Studies" to /customers; CoreX logo to a working URL.

      Software Engineer 1 hour

    2. 2

      Merge Valiantys

      One page, 301 from the other.

      Software Engineer 1 hour

    3. 3

      Retitle

      Outcome-led titles and meta descriptions for every story.

      Founder (go-to-market) 1 day

    4. 4

      Move paths

      /customers/<name> with redirects from /blog.

      Software Engineer 1 day

    5. 5

      Check logo links

      A monthly check that all 14 logo links resolve.

      Software Engineer monthly

    6. 6

      Measure

      Story views and demo clicks from stories.

      Founder (go-to-market) monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founder (go to market)

    Smallest test

    Retitle three stories and compare their clicks after a month.

    Why it works

    Give every story an outcome title ("How CoreX keeps one format across regions"), merge /blog/valiantys into /blog/valiantys-case-study with a 301, point the footer link at /customers, and change the CoreX logo link to its working page. Move customer stories to a /customers/<name> path so they stop competing with blog posts.

    Outcome titles are what buyers scan and what search engines show. One page per customer avoids splitting links and attention.

    Risks and how to handle them

    • Redirects lose links

      301 every old URL to its new path.

    Evidence

    • Your websiteCustomers page: 13 stories (2 "Customer Stories", 11 "Case Studies"); only Softype shows a result in its summary ("$2-3M in pipeline"); the four "By the numbers" figures (90% less time getting up to speed, 70% faster story and requirements finalization, 10+ hours saved per person per week, 80% quicker artifact creation) are not tied to any customer; Valiantys appears twice (/blog/valiantys and /blog/valiantys-case-study); titles such as "CoreX and Auctor" and "NTT and Auctor" carry no outcome; there is no filter by ecosystem, although the stories span NetSuite, ServiceNow, Salesforce, Atlassian, OneStream and SAP.Source
    • Your websitePartner stories without figures: NTT DATA Business Solutions' life sciences consultants use Auctor across SAP scoping, design, build and delivery (September 1, 2026); CoreX is "An Elite ServiceNow Partner" with a "global team of 200+ employees". The homepage CoreX logo links to corexcorp.com, which returned 404 when checked on November 9, 2026.Source
    • Your websiteBook-a-demo page: the heading "Book a Demo" and ten customer logos, with no testimonials, figures, video, product tour or sandbox. Resources page: press, 12 blog posts (including "The Customer Portal That Ends the Two Versions of the Truth"), 8 case studies and 6 workflow pages; no newsletter signup and no webinar library; the footer link labelled "Case Studies" goes to /resources.Source
  • 04

    The October 7 webinar "Where SAP Implementations Lose Margin Before Configuration Starts" was recorded and emailed only to registrants, and the resources page has no webinar library. SAP is one of Auctor's newest ecosystems (NTT DATA's life sciences practice joined on September 1). Right now the recording reaches only the people who already signed up.

    Medium impactLow effort First result in 2 weeks Founder

    First action

    Upload the recording and write the chapter list.

    How to measure it

    SAP recording demos

    Now
    –
    Target
    5 demos
    By
    60 days

    Steps

    1. 1

      Edit the recording

      Remove attendee faces and names if not cleared; add chapters.

      Founder (go-to-market) 1 day

    2. 2

      Write the summary

      Five takeaways in text, for search and skimmers.

      Founder (go-to-market) half a day

    3. 3

      Cut three clips

      One per theme, under 90 seconds.

      Founder (go-to-market) 1 day

    4. 4

      Publish

      On the SAP page, with a demo CTA after each chapter.

      Software Engineer half a day

    5. 5

      Distribute

      LinkedIn, registrants who missed it, and SAP partners' networks.

      Founding Account Executive 1 week

    6. 6

      Repeat

      Every future webinar gets the same page within a week.

      Founder (go-to-market) ongoing

    First result
    2 weeks
    Cost
    $0
    Owner
    Founder (go to market)

    Smallest test

    Post one clip on LinkedIn and count demo clicks.

    Why it works

    Post the recording on the SAP ecosystem page with chapters, a short written summary, and three clips: Fit-to-Standard decisions, change requests against agreed requirements, and the handoff to delivery. Add a demo CTA after each chapter, and send the clips to the NTT DATA team to share with their network.

    A practitioner talk on margin is evergreen for SAP services leaders. Ungated, it can rank and be forwarded, which a registrant-only email never will.

    Risks and how to handle them

    • Speakers didn't agree to public release

      Ask them first, or publish the slides and summary only.

    Builds on

    Evidence

    • Your websiteEvent pages still live after the events: the SAP webinar "Where SAP Implementations Lose Margin Before Configuration Starts" (October 7, 2026; "The recording will be emailed to all registered participants"); "Meet us at SuiteWorld" (October 25–28, 2026), covering "Auctor in the NetSuite ecosystem" with Bring IT, Myers Holum and Softype and the offer "Bring us your hardest implementation problem"; a Dreamforce 5K on September 15; and "Full Context at Knowledge 26", an invitation-only dinner in ServiceNow's conference week on May 4, 2026, "third in the series, after Chicago and New York".Source
    • Your websitePartner stories without figures: NTT DATA Business Solutions' life sciences consultants use Auctor across SAP scoping, design, build and delivery (September 1, 2026); CoreX is "An Elite ServiceNow Partner" with a "global team of 200+ employees". The homepage CoreX logo links to corexcorp.com, which returned 404 when checked on November 9, 2026.Source
    • Your websiteBook-a-demo page: the heading "Book a Demo" and ten customer logos, with no testimonials, figures, video, product tour or sandbox. Resources page: press, 12 blog posts (including "The Customer Portal That Ends the Two Versions of the Truth"), 8 case studies and 6 workflow pages; no newsletter signup and no webinar library; the footer link labelled "Case Studies" goes to /resources.Source
  • 05

    The only way to see Auctor is to book a demo. The demo page has a heading and ten logos but no video, tour or sandbox. The six workflow pages, such as "Defensible Backlog", describe the product in words with no video and no figures. Technical buyers at SIs want to see the product before giving up an hour, and the Founding AE runs demos without a sales engineer.

    High impactLow effort First result in 2 weeks Product Manager

    First action

    Record the "Your Discovery Call Writes Itself" walkthrough on a sample project.

    How to measure it

    Demo page form completion

    Now
    –
    Target
    +20%
    By
    60 days

    Steps

    1. 1

      Build a sample project

      Fictional client data, no customer content.

      Deployment Strategist 2 days

    2. 2

      Script six walkthroughs

      One per workflow page, under three minutes.

      Product Manager 1 day

    3. 3

      Record

      Screen plus voice, captions on.

      Product Manager 2 days

    4. 4

      Embed

      Workflow pages and the demo page, lazy-loaded.

      Software Engineer 1 day

    5. 5

      Add a form question

      "Which workflow matters most?"

      Founding Account Executive 1 hour

    6. 6

      Track

      Play rate and form completion with and without a view.

      Product Manager monthly

    First result
    2 weeks
    Cost
    Under $500 for recording tools
    Owner
    Product Manager

    Smallest test

    Put one walkthrough on the demo page for two weeks and compare form completions.

    Why it works

    Record one short screen walkthrough per workflow (discovery call to requirements, SOW draft, scope-drift flag, status pulse) on a realistic sample project. Put each on its workflow page and a two-minute overview on the demo page next to the form. Lazy-load the videos so the homepage, already 2.2 MB in the lab test, doesn't get heavier. Ask on the form which workflow the visitor watched, so the demo starts there.

    Seeing the artifact being made is Auctor's strongest argument. Pre-watched demos are shorter, better qualified and easier for one AE to run.

    Risks and how to handle them

    • Videos go stale as the product ships

      Re-record each quarter; keep them short.

    • Competitors study the product

      Show outcomes and flow, not configuration detail.

    Evidence

    • Your websiteBook-a-demo page: the heading "Book a Demo" and ten customer logos, with no testimonials, figures, video, product tour or sandbox. Resources page: press, 12 blog posts (including "The Customer Portal That Ends the Two Versions of the Truth"), 8 case studies and 6 workflow pages; no newsletter signup and no webinar library; the footer link labelled "Case Studies" goes to /resources.Source
    • Your websiteWorkflow and delivery pages: "Defensible Backlog" shows a Routine that checks each new request against the Statement of Work and flags drift, with no video and no figures; the /delivery page ("The handoff shouldn't reset the engagement.") sets Auctor against general-purpose AI tools and links the ServiceRocket story.Source
    • PageSpeedPageSpeed (November 9, 2026): mobile 89, desktop 74; real visitors pass Core Web Vitals (field LCP 1.8 s, CLS 0); in the lab test the homepage weighs 2.2 MB with 807 KB of JavaScript and about 4.7 s of render-blocking requests; seven third-party tools load, including PostHog, Google Tag Manager, Google Analytics, HubSpot and LinkedIn Ads.Source
    • HiringFounding Account Executive (New York, posted February 6, 2026): "Own the sales process from prospecting to close, targeting emerging, mid-market, and enterprise Systems Integrators", running discovery and demos for technical audiences without a Sales Engineer on every call; Auctor automates work that "powers $400B+ in services work".Source
  • 06

    Auctor publishes steadily: 20 blog posts since May, partner announcements roughly every few weeks, product workflows, press and investor posts. The resources page has no newsletter signup, so a services leader who likes a post has no way to hear about the next one except by booking a demo.

    Medium impactLow effort First result in 1 month Founder

    First action

    Add the signup form to /resources using the existing HubSpot account.

    How to measure it

    Subscribers at SIs and implementation partners

    Now
    –
    Target
    500
    By
    2 quarters

    Steps

    1. 1

      Add the form

      One field plus an optional ecosystem picker.

      Software Engineer half a day

    2. 2

      Place it

      Resources, blog posts and workflow pages.

      Software Engineer half a day

    3. 3

      Write issue one

      A result, a workflow, an event, an idea.

      Founder (go-to-market) 1 day

    4. 4

      Invite past contacts

      Event registrants and webinar attendees who opted in.

      Founding Account Executive 1 day

    5. 5

      Flag warm accounts

      Alert the AE when three people from one firm subscribe.

      Founding Account Executive ongoing

    6. 6

      Review

      Open and reply rates each month.

      Founder (go-to-market) monthly

    First result
    1 month
    Cost
    $0 with existing HubSpot
    Owner
    Founder (go to market)

    Smallest test

    Add the form to /resources and count signups for a month.

    Why it works

    Add a one-field signup to the resources page, every blog post and the workflow pages. Send a monthly note for implementation leaders: one new customer result, one workflow, one ecosystem event, and one short practitioner idea (such as "The Rise of the Full Stack Consultant"). Tag subscribers by ecosystem so the AE can see warm accounts.

    Most SI leaders aren't ready for a demo on their first visit. A monthly note keeps Auctor in front of them until a scoping or handoff problem makes them ready.

    Risks and how to handle them

    • No time to write monthly

      Reuse that month's blog and partner posts; keep it to 300 words.

    Evidence

    • Your websiteBook-a-demo page: the heading "Book a Demo" and ten customer logos, with no testimonials, figures, video, product tour or sandbox. Resources page: press, 12 blog posts (including "The Customer Portal That Ends the Two Versions of the Truth"), 8 case studies and 6 workflow pages; no newsletter signup and no webinar library; the footer link labelled "Case Studies" goes to /resources.Source
    • Your websiteSitemap (52 URLs, checked November 9, 2026): event pages for Workday Rising (three), Dreamforce (three), SuiteWorld (two), ServiceNow Knowledge 26 and an SAP webinar; two integration pages (/hubspot-integration, /slack-integration); customer stories and partner posts filed under /blog; six /workflow pages; no ecosystem, comparison, pricing, integrations-directory or changelog pages.Source
    • HiringOpen roles (Ashby, November 9, 2026): 11, all on-site in New York: six in engineering (including Forward Deployed Engineer and Software Engineer, Applied AI), two in product, a Founding Account Executive, a Customer Success Manager and a Deployment Strategist; no marketing role.Source

This quarter 13

The core plays for the next three months.

  • 07

    The Founding AE sells to emerging, mid-market and enterprise SIs and runs technical demos alone. The demo page shows no qualification questions, so every demo starts cold. Auctor already has peer stories by ecosystem: Softype for NetSuite, NTT DATA for SAP, CoreX for ServiceNow.

    High impactLow effort First result in 1 month Founding Account Executive

    First action

    Add the ecosystem question to the form.

    How to measure it

    Demo-to-opportunity conversion

    Now
    –
    Target
    +25%
    By
    1 quarter

    Steps

    1. 1

      Add questions

      Ecosystem, consultant count, role.

      Software Engineer half a day

    2. 2

      Write briefs

      One page per ecosystem: peer story, workflow, likely objection.

      Founding Account Executive 2 days

    3. 3

      Set routing

      By firm size in HubSpot.

      Founding Account Executive 1 day

    4. 4

      Confirmation email

      Sends the matching story.

      Founding Account Executive half a day

    5. 5

      Review calls

      Which briefs led to second meetings.

      Founding Account Executive weekly

    6. 6

      Report

      Conversion by ecosystem and size.

      Founding Product Operations Manager monthly

    First result
    1 month
    Cost
    $0
    Owner
    Founding Account Executive

    Smallest test

    Add only the ecosystem question for two weeks.

    Why it works

    Add three required picks to the form: primary ecosystem, number of consultants, and role (pre-sales, delivery, practice lead). Route the request: enterprise SIs to a founder-led call, and the rest to the AE with an auto-attached one-page brief that holds the matching peer story and the workflow to show first. Send a confirmation email with that peer story so the prospect arrives warmed up.

    Relevance in the first five minutes decides technical demos. A one-person sales team can't afford discovery that the form could have done.

    Risks and how to handle them

    • More fields, fewer submissions

      Use picklists, not text boxes; test completion rate.

    Evidence

    • HiringFounding Account Executive (New York, posted February 6, 2026): "Own the sales process from prospecting to close, targeting emerging, mid-market, and enterprise Systems Integrators", running discovery and demos for technical audiences without a Sales Engineer on every call; Auctor automates work that "powers $400B+ in services work".Source
    • Your websiteBook-a-demo page: the heading "Book a Demo" and ten customer logos, with no testimonials, figures, video, product tour or sandbox. Resources page: press, 12 blog posts (including "The Customer Portal That Ends the Two Versions of the Truth"), 8 case studies and 6 workflow pages; no newsletter signup and no webinar library; the footer link labelled "Case Studies" goes to /resources.Source
    • Your websiteCustomers page: 13 stories (2 "Customer Stories", 11 "Case Studies"); only Softype shows a result in its summary ("$2-3M in pipeline"); the four "By the numbers" figures (90% less time getting up to speed, 70% faster story and requirements finalization, 10+ hours saved per person per week, 80% quicker artifact creation) are not tied to any customer; Valiantys appears twice (/blog/valiantys and /blog/valiantys-case-study); titles such as "CoreX and Auctor" and "NTT and Auctor" carry no outcome; there is no filter by ecosystem, although the stories span NetSuite, ServiceNow, Salesforce, Atlassian, OneStream and SAP.Source
  • 08

    The product page lists 19 integrations, but only HubSpot and Slack have their own pages. The HubSpot page is a good model: it explains exactly what the agent can read and write, how a deal links to a project, and that writes need approval. Consultants search "<tool> + requirements" or "Gong to SOW", and the other 17 integrations have no page to land on.

    Medium impactMedium effort First result in 2 months Software Engineer

    First action

    Write the Salesforce page from the HubSpot template.

    How to measure it

    Integration page visits

    Now
    –
    Target
    1,000 a month
    By
    2 quarters

    Steps

    1. 1

      Rank integrations

      By use in current accounts and deals.

      Founding Product Operations Manager 1 day

    2. 2

      Template

      Reads, writes, approvals, clip, setup.

      Software Engineer 2 days

    3. 3

      Write five pages

      Salesforce, Gong, Jira, Azure DevOps, Certinia.

      Software Engineer 2 weeks

    4. 4

      Build the directory

      /integrations, linked from the product page.

      Software Engineer 2 days

    5. 5

      Review with security

      Permissions wording.

      Senior Software Engineer, Backend 2 days

    6. 6

      Finish the rest

      Remaining integrations, two a week.

      Software Engineer 6 weeks

    First result
    2 months
    Cost
    Engineering time
    Owner
    Software Engineer

    Smallest test

    Publish the Salesforce page and share it in two late-stage deals.

    Why it works

    Use the HubSpot page as the template for each integration: what Auctor reads, what it writes, approval controls, a 60-second clip and a setup guide. Start with the integrations closest to the money: Salesforce and Gong (pre-sales), Jira and Azure DevOps (delivery) and Certinia (PSA). Add an /integrations directory and link it from the product page.

    Integration pages answer the IT and security questions that stall technical deals. They also catch searches from consultants who already use those tools.

    Risks and how to handle them

    • Pages go stale as connectors change

      Generate the reads and writes list from connector config.

    Evidence

    • Your websiteProduct page: Capture, Contextualize, Create; features include "Proof of performance", "Trace every requirement", "Draft smarter with AI" (first drafts of SOWs, scopes and designs) and "Standardize every implementation"; 19 integrations listed, among them Salesforce, Gong, HubSpot, Certinia, Jira, Confluence, Azure DevOps, Linear, Rally, Slack, Microsoft Teams and Zoom; the page names none of NetSuite, Workday, SAP or ServiceNow.Source
    • Your websiteHubSpot integration page: a setup guide under Resources; Auctor's agent can answer questions about, create and update HubSpot contacts, companies, deals and tickets and link a deal to an Auctor project; writes need user approval by default.Source
    • Your websiteSitemap (52 URLs, checked November 9, 2026): event pages for Workday Rising (three), Dreamforce (three), SuiteWorld (two), ServiceNow Knowledge 26 and an SAP webinar; two integration pages (/hubspot-integration, /slack-integration); customer stories and partner posts filed under /blog; six /workflow pages; no ecosystem, comparison, pricing, integrations-directory or changelog pages.Source
  • 09

    Rocketlane now sells an "agentic, all-in-one PSA" whose agents generate project plans from SOWs and calls, and Kantata sells an AI that "learns how your firm delivers its best work". Services firms already pay for a PSA, so Auctor looks like one more AI tool. Its real gap is upstream: discovery, decisions and traceability before the plan exists. Certinia is already in its integration list.

    High impactMedium effort First result in 6 weeks Founder

    First action

    List the PSAs current customers use.

    How to measure it

    PSA-objection losses

    Now
    –
    Target
    -50%
    By
    2 quarters

    Steps

    1. 1

      Survey customers

      Which PSA they run and how Auctor fits.

      Customer Success Manager 1 week

    2. 2

      Check facts

      Each PSA's current features from its own site.

      Founder (go-to-market) 2 days

    3. 3

      Write the pages

      Division of labor, data flow, fair table.

      Founder (go-to-market) 1 week

    4. 4

      Legal review

      Trademarks and claims.

      Outside counsel 3 days

    5. 5

      Train the AE

      Objection script and the diagram.

      Founding Account Executive 1 day

    6. 6

      Refresh

      Every quarter, dated.

      Founder (go-to-market) quarterly

    First result
    6 weeks
    Cost
    Staff time plus a legal review
    Owner
    Founder (go to market)

    Smallest test

    Use the complement framing in the next five deals that mention a PSA.

    Why it works

    Write one page per major PSA (Rocketlane, Kantata, Certinia) that explains the division of labor. The PSA runs resources, time and billing. Auctor captures discovery, drafts the SOW and keeps every requirement traceable, then hands a clean scope to the PSA. Include a fair comparison table of where each fits, and a two-way data flow diagram. Train the AE to use the same framing when a prospect says "we already have a PSA".

    "Do we need another tool?" is the main objection. A complement story removes it, and it catches high-intent searches for PSA comparisons.

    Risks and how to handle them

    • A PSA adds discovery features

      Lead with traceability across the lifecycle, which a planning agent alone doesn't give.

    Evidence

    • Competitor researchRivals' own homepages: Rocketlane, "Deliver radical efficiency with an agentic, all-in-one PSA", whose Nitro agents "auto-generate project plans" from SOWs, emails and calls, with a free trial; Kantata, a "Professional Services Automation Platform" whose AI "learns how your firm delivers its best work", for mid-market and enterprise services firms.Source
    • Your websiteProduct page: Capture, Contextualize, Create; features include "Proof of performance", "Trace every requirement", "Draft smarter with AI" (first drafts of SOWs, scopes and designs) and "Standardize every implementation"; 19 integrations listed, among them Salesforce, Gong, HubSpot, Certinia, Jira, Confluence, Azure DevOps, Linear, Rally, Slack, Microsoft Teams and Zoom; the page names none of NetSuite, Workday, SAP or ServiceNow.Source
    • Your websiteSitemap (52 URLs, checked November 9, 2026): event pages for Workday Rising (three), Dreamforce (three), SuiteWorld (two), ServiceNow Knowledge 26 and an SAP webinar; two integration pages (/hubspot-integration, /slack-integration); customer stories and partner posts filed under /blog; six /workflow pages; no ecosystem, comparison, pricing, integrations-directory or changelog pages.Source
  • 10

    Weidenhammer found a competing AI tool captured only 40-50% of what was discussed in meetings, and the /delivery page already sets Auctor against general-purpose AI tools. But that comparison exists only as one line in one story, and the cheapest alternative for any SI is the AI assistant already on every laptop.

    Medium impactMedium effort First result in 2 months Product Manager

    First action

    Build the scoring sheet for one sample workshop.

    How to measure it

    Capture-test pilots

    Now
    –
    Target
    8
    By
    2 quarters

    Steps

    1. 1

      Build the sample

      A realistic fictional workshop recording.

      Deployment Strategist 1 week

    2. 2

      Define the answer key

      Requirements and decisions a senior consultant would log.

      Deployment Strategist 2 days

    3. 3

      Run the test

      Auctor and common general-purpose tools.

      Product Manager 1 week

    4. 4

      Publish the method

      Page with method, sample and results.

      Product Manager 1 week

    5. 5

      Offer it in deals

      Run it on a prospect's own call.

      Founding Account Executive ongoing

    6. 6

      Re-run

      Each quarter as tools change.

      Product Manager quarterly

    First result
    2 months
    Cost
    Staff time
    Owner
    Product Manager

    Smallest test

    Run the test on one sample and share it in three deals.

    Why it works

    Turn the Weidenhammer finding into a public method: take a recorded sample discovery workshop, list every requirement and decision a senior consultant would capture, and score how many each tool captures and traces into a draft SOW. Publish the method, the sample and Auctor's score, and invite prospects to run it on one of their own calls during a pilot.

    A test buyers can repeat beats any claim, and it moves the comparison from "AI vs AI" to "what did you miss", where traceability wins.

    Risks and how to handle them

    • Seen as a rigged test

      Publish the sample and answer key so anyone can re-run it.

    Evidence

    • Your websiteWeidenhammer case study (a mid-market ERP and e-commerce implementer): RFPs and SOWs "that once took hours now take minutes"; a competing AI tool captured only 40-50% of the information discussed in meetings; a VP: "Auctor hasn't just improved our efficiency — it's elevated the standard of work we deliver to our clients."Source
    • Your websiteWorkflow and delivery pages: "Defensible Backlog" shows a Routine that checks each new request against the Statement of Work and flags drift, with no video and no figures; the /delivery page ("The handoff shouldn't reset the engagement.") sets Auctor against general-purpose AI tools and links the ServiceRocket story.Source
  • 11

    The SuiteWorld page offered meetings where partners "Bring us your hardest implementation problem" and see how Auctor handles it. That offer is better than "Book a Demo", but it lived for four days in Las Vegas. The new Deployment Strategist's job is to learn each customer's methodology and configure Auctor's agents to it, which is exactly the skill a teardown needs.

    High impactMedium effort First result in 1 month Deployment Strategist

    First action

    Write the teardown offer page and the intake checklist.

    How to measure it

    Teardowns that become pilots

    Now
    –
    Target
    30%
    By
    2 quarters

    Steps

    1. 1

      Define the deliverable

      Requirements, decisions and risks from one input.

      Deployment Strategist 2 days

    2. 2

      Set data rules

      Anonymized inputs only, deletion after the session.

      Senior Software Engineer, Backend 2 days

    3. 3

      Build the page

      Offer, intake, booking.

      Software Engineer 2 days

    4. 4

      Run five

      With existing pipeline accounts.

      Deployment Strategist 2 weeks

    5. 5

      Promote

      Ecosystem pages, newsletter, outreach.

      Founding Account Executive ongoing

    6. 6

      Track

      Teardown to pilot and close.

      Founding Product Operations Manager monthly

    First result
    1 month
    Cost
    Deployment Strategist time
    Owner
    Deployment Strategist

    Smallest test

    Offer teardowns to ten SuiteWorld contacts who didn't book.

    Why it works

    Offer a 45-minute teardown year-round. The SI shares one anonymized discovery transcript or messy SOW, and the Deployment Strategist returns structured requirements, open decisions and scope risks produced in Auctor, then walks through them live. Cap it at a few a week and qualify by firm size. Promote it on the ecosystem pages, in the newsletter and in AE outreach.

    Prospects see their own work transformed, which is the strongest demo there is. It also teaches the team which artifacts each ecosystem needs most.

    Risks and how to handle them

    • Too many low-fit requests

      Qualify by consultant count and ecosystem; cap weekly slots.

    • Confidential client data

      Require anonymized inputs and state the deletion policy.

    Evidence

    • Your websiteEvent pages still live after the events: the SAP webinar "Where SAP Implementations Lose Margin Before Configuration Starts" (October 7, 2026; "The recording will be emailed to all registered participants"); "Meet us at SuiteWorld" (October 25–28, 2026), covering "Auctor in the NetSuite ecosystem" with Bring IT, Myers Holum and Softype and the offer "Bring us your hardest implementation problem"; a Dreamforce 5K on September 15; and "Full Context at Knowledge 26", an invitation-only dinner in ServiceNow's conference week on May 4, 2026, "third in the series, after Chicago and New York".Source
    • HiringDeployment Strategist (New York, posted September 24, 2026): "Meet with customer teams to understand their implementation methodology, pain points, and critical deliverables" and "Configure and customize Auctor's AI agents to match customer workflows and artifact requirements".Source
    • Your websiteBook-a-demo page: the heading "Book a Demo" and ten customer logos, with no testimonials, figures, video, product tour or sandbox. Resources page: press, 12 blog posts (including "The Customer Portal That Ends the Two Versions of the Truth"), 8 case studies and 6 workflow pages; no newsletter signup and no webinar library; the footer link labelled "Case Studies" goes to /resources.Source
  • 12

    The new Customer Success Manager is asked to "Build and present ROI narratives that connect Auctor usage (sessions, artifacts generated, active users) to real outcomes" across a portfolio of SIs. If this is done by hand for each QBR, it won't scale. Built once, it also produces the numbers the customer stories are missing.

    High impactMedium effort First result in 1 quarter Customer Success Manager

    First action

    Agree the hours-saved rate per artifact type with two friendly customers.

    How to measure it

    Accounts with a delivered ROI report

    Now
    –
    Target
    100% of accounts
    By
    1 quarter

    Steps

    1. 1

      Agree the method

      Hours saved per artifact type, with customers.

      Customer Success Manager 1 week

    2. 2

      Build the data

      Usage metrics per account.

      Software Engineer 2 weeks

    3. 3

      Design the report

      One page for the practice lead.

      Product Manager 1 week

    4. 4

      Pilot

      Five accounts before their QBRs.

      Customer Success Manager 1 month

    5. 5

      Roll out

      All accounts each quarter.

      Customer Success Manager quarterly

    6. 6

      Feed proof

      Ask for permission to publish the best results.

      Customer Success Manager quarterly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Customer Success Manager

    Smallest test

    Make a hand-built report for two accounts before their next QBR.

    Why it works

    Build a standard in-app report per account: sessions captured, artifacts generated by type, active users, estimated hours saved (using an agreed rate per artifact) and scope changes flagged. The CSM adds two lines of context and the customer's own outcome, such as RFPs won or a smaller project team. The report goes to the practice lead before each QBR and renewal. With permission, the best results feed the customers page.

    Services firms renew tools that show margin. A standard report makes value visible to the economic buyer, not just the daily users.

    Risks and how to handle them

    • Hours-saved estimates questioned

      Show the method and let each customer set its own rate.

    Evidence

    • HiringCustomer Success Manager (New York, posted September 14, 2026): "Manage onboarding, adoption, health checks, QBRs, and renewals" for "a portfolio of implementation partners and systems integrators", and "Build and present ROI narratives that connect Auctor usage (sessions, artifacts generated, active users) to real outcomes".Source
    • Your websiteCustomers page: 13 stories (2 "Customer Stories", 11 "Case Studies"); only Softype shows a result in its summary ("$2-3M in pipeline"); the four "By the numbers" figures (90% less time getting up to speed, 70% faster story and requirements finalization, 10+ hours saved per person per week, 80% quicker artifact creation) are not tied to any customer; Valiantys appears twice (/blog/valiantys and /blog/valiantys-case-study); titles such as "CoreX and Auctor" and "NTT and Auctor" carry no outcome; there is no filter by ecosystem, although the stories span NetSuite, ServiceNow, Salesforce, Atlassian, OneStream and SAP.Source
  • 13

    Auctor's product promise is "Standardize every implementation" and "Your best work, codified forever", and the Deployment Strategist configures agents to each customer's methodology and artifact requirements. Softype's founder wants "all the knowledge of the company" inside Auctor. Nothing public shows how fast a new firm gets there. The first artifact a consultant sends to a client is the moment adoption sticks.

    High impactMedium effort First result in 1 quarter Deployment Strategist

    First action

    Measure days to first client-ready artifact for the last ten accounts.

    How to measure it

    Time to first client-ready artifact

    Now
    –
    Target
    Under 7 days
    By
    1 quarter

    Steps

    1. 1

      Baseline

      Last ten onboardings.

      Founding Product Operations Manager 2 days

    2. 2

      Week-one plan

      Templates, connectors, one live session.

      Deployment Strategist 1 week

    3. 3

      Instrument

      Flag when an artifact is shared with a client.

      Software Engineer 1 week

    4. 4

      Build starter kits

      NetSuite, ServiceNow and SAP templates.

      Forward Deployed Engineer 1 month

    5. 5

      Run with new accounts

      Every onboarding this quarter.

      Deployment Strategist 1 quarter

    6. 6

      Review

      Slow accounts and why.

      Customer Success Manager monthly

    First result
    1 quarter
    Cost
    Staff time
    Owner
    Deployment Strategist

    Smallest test

    Run the week-one plan with the next two new accounts.

    Why it works

    Set a week-one standard: import the firm's templates (SOW, requirements, status report), connect the call recorder and CRM, and run one live discovery session that produces a client-ready artifact. Track "days to first client-ready artifact" for every new account. Use the pattern from the fastest accounts to build ecosystem starter kits, so a NetSuite firm starts with NetSuite-shaped templates.

    Fast first value predicts adoption and renewal. Starter kits also cut the Deployment Strategist's time per account as the customer count grows.

    Risks and how to handle them

    • Customers lack templates

      Offer the ecosystem starter kit as the default.

    Evidence

    • HiringDeployment Strategist (New York, posted September 24, 2026): "Meet with customer teams to understand their implementation methodology, pain points, and critical deliverables" and "Configure and customize Auctor's AI agents to match customer workflows and artifact requirements".Source
    • Your websiteProduct page: Capture, Contextualize, Create; features include "Proof of performance", "Trace every requirement", "Draft smarter with AI" (first drafts of SOWs, scopes and designs) and "Standardize every implementation"; 19 integrations listed, among them Salesforce, Gong, HubSpot, Certinia, Jira, Confluence, Azure DevOps, Linear, Rally, Slack, Microsoft Teams and Zoom; the page names none of NetSuite, Workday, SAP or ServiceNow.Source
    • Your websiteSoftype case study (a NetSuite-only consultancy): "$2–3M in client opportunities quoted (YTD)"; RFP turnaround cut from "~2–3 weeks to 1–2 days"; RFP team from 2–3 people to 1; "About 40 discovery questions generated in 30 seconds"; the founder: "Having Auctor feels like having a few extra people working on these tasks with great ease and consistency."Source
  • 14

    Many stories start in pre-sales: ServiceRocket "Unifies Discovery and Proposal", Softype quotes RFPs faster, Weidenhammer speeds SOWs. Auctor's /delivery page argues "The handoff shouldn't reset the engagement." Each won deal is a moment when a new team, delivery, inherits the work. That is the natural point to add delivery seats.

    High impactMedium effort First result in 1 quarter Customer Success Manager

    First action

    List accounts where only pre-sales users are active.

    How to measure it

    Pre-sales accounts expanded to delivery

    Now
    –
    Target
    40%
    By
    2 quarters

    Steps

    1. 1

      Segment accounts

      Pre-sales-only versus both teams.

      Founding Product Operations Manager 2 days

    2. 2

      Build the trigger

      Deal closed in the CRM link starts the handoff package.

      Software Engineer 2 weeks

    3. 3

      Write the package

      What was sold, by whom and why, in one view.

      Product Manager 1 week

    4. 4

      Offer a trial

      Delivery team on one project, Routines on.

      Customer Success Manager ongoing

    5. 5

      Show results

      Drift caught and hours saved after 30 days.

      Customer Success Manager 30 days

    6. 6

      Propose seats

      Practice-wide delivery license.

      Founding Account Executive ongoing

    First result
    1 quarter
    Cost
    Staff and engineering time
    Owner
    Customer Success Manager

    Smallest test

    Offer a delivery trial on the next three deals won in Auctor.

    Why it works

    When a customer's deal created in Auctor closes, trigger a handoff package: the delivery lead gets the traceable record of what was sold, and the CSM offers a delivery-team trial on that one project, with scope-drift Routines switched on. After 30 days, show drift caught and rework avoided, and propose delivery seats across the practice.

    Expansion is cheaper than new logos, and the handoff is when the value of the pre-sales record is most obvious to delivery.

    Risks and how to handle them

    • Delivery uses other tools

      Lead with Jira and Azure DevOps sync so Auctor feeds their tools.

    Builds on

    Evidence

    • Your websiteWorkflow and delivery pages: "Defensible Backlog" shows a Routine that checks each new request against the Statement of Work and flags drift, with no video and no figures; the /delivery page ("The handoff shouldn't reset the engagement.") sets Auctor against general-purpose AI tools and links the ServiceRocket story.Source
    • Your websiteSoftype case study (a NetSuite-only consultancy): "$2–3M in client opportunities quoted (YTD)"; RFP turnaround cut from "~2–3 weeks to 1–2 days"; RFP team from 2–3 people to 1; "About 40 discovery questions generated in 30 seconds"; the founder: "Having Auctor feels like having a few extra people working on these tasks with great ease and consistency."Source
    • Your websiteHubSpot integration page: a setup guide under Resources; Auctor's agent can answer questions about, create and update HubSpot contacts, companies, deals and tickets and link a deal to an Auctor project; writes need user approval by default.Source
  • 15

    SIs inside one ecosystem know each other: they meet at SuiteWorld, Knowledge and Workday Rising, subcontract and hire from each other. Auctor already has clusters: three NetSuite partners featured together at SuiteWorld, and Myers-Holum "expands its partnership" with Auctor. There is no referral program on the site.

    Medium impactLow effort First result in 2 months Founding Account Executive

    First action

    Ask the three most active customers which partner firms they would introduce.

    How to measure it

    Referral-sourced pilots

    Now
    –
    Target
    6
    By
    2 quarters

    Steps

    1. 1

      Pick the reward

      Service credit or seats per referred pilot.

      Founder (go-to-market) 1 day

    2. 2

      Write the forward note

      One per ecosystem.

      Founding Account Executive 1 day

    3. 3

      Ask champions

      In QBRs and after wins.

      Customer Success Manager ongoing

    4. 4

      Track

      Referral source field in the CRM.

      Founding Account Executive 1 hour

    5. 5

      Thank publicly

      With permission, in the newsletter.

      Founder (go-to-market) monthly

    6. 6

      Review

      Referrals per ecosystem.

      Founding Account Executive quarterly

    First result
    2 months
    Cost
    Service credits only
    Owner
    Founding Account Executive

    Smallest test

    Ask five champions for one introduction each.

    Why it works

    Offer existing customers a reward for each referred firm that starts a pilot: a service credit or extra seats, which suit services firms better than cash. Give each champion a short ecosystem-specific note they can forward, and an invite to the next Full Context dinner for the referred firm's leader. Track referrals by ecosystem.

    Peer referrals inside a tight ecosystem convert far better than outbound, and a single AE can't cover every partner in every ecosystem.

    Risks and how to handle them

    • Customers don't want to help competitors

      Ask for referrals in adjacent ecosystems or regions, and for partners they work with.

    Evidence

    • Your websiteEvent pages still live after the events: the SAP webinar "Where SAP Implementations Lose Margin Before Configuration Starts" (October 7, 2026; "The recording will be emailed to all registered participants"); "Meet us at SuiteWorld" (October 25–28, 2026), covering "Auctor in the NetSuite ecosystem" with Bring IT, Myers Holum and Softype and the offer "Bring us your hardest implementation problem"; a Dreamforce 5K on September 15; and "Full Context at Knowledge 26", an invitation-only dinner in ServiceNow's conference week on May 4, 2026, "third in the series, after Chicago and New York".Source
    • Your websiteCustomers page: 13 stories (2 "Customer Stories", 11 "Case Studies"); only Softype shows a result in its summary ("$2-3M in pipeline"); the four "By the numbers" figures (90% less time getting up to speed, 70% faster story and requirements finalization, 10+ hours saved per person per week, 80% quicker artifact creation) are not tied to any customer; Valiantys appears twice (/blog/valiantys and /blog/valiantys-case-study); titles such as "CoreX and Auctor" and "NTT and Auctor" carry no outcome; there is no filter by ecosystem, although the stories span NetSuite, ServiceNow, Salesforce, Atlassian, OneStream and SAP.Source
    • HiringFounding Account Executive (New York, posted February 6, 2026): "Own the sales process from prospecting to close, targeting emerging, mid-market, and enterprise Systems Integrators", running discovery and demos for technical audiences without a Sales Engineer on every call; Auctor automates work that "powers $400B+ in services work".Source
  • 16

    "Full Context at Knowledge 26" was the third invitation-only dinner for senior services and SI leaders, after Chicago and New York. It promises no panels, pitches or recordings. Dinners like this suit a buyer group of practice leaders, but three a year is a slow cadence for a company with one AE.

    Medium impactMedium effort First result in 1 month Founder

    First action

    Set the next three dates and choose the host customer for each.

    How to measure it

    Opportunities from dinner guests

    Now
    –
    Target
    3 per dinner
    By
    2 quarters

    Steps

    1. 1

      Plan the calendar

      Conference weeks and customer cities.

      Founder (go-to-market) 1 day

    2. 2

      Recruit hosts

      One customer leader per dinner.

      Customer Success Manager 2 weeks

    3. 3

      Build guest lists

      Target firms by ecosystem.

      Founding Account Executive 2 weeks

    4. 4

      Host

      No pitch, one theme.

      Founder (go-to-market) monthly

    5. 5

      Send the note

      Unattributed themes, within a week.

      Founder (go-to-market) 1 day

    6. 6

      Follow up

      Teardown offer to every guest.

      Founding Account Executive 1 week

    First result
    1 month
    Cost
    $3,000-6,000 per dinner
    Owner
    Founder (go to market)

    Smallest test

    Host one dinner in New York with a customer host.

    Why it works

    Run one dinner a month: alternate ecosystem conference weeks with cities where customers cluster. Invite eight to twelve practice leaders, with one customer host per table. Afterwards, send guests (and newsletter readers, unattributed) a short note on the themes discussed, such as margin lost in discovery or scope drift. The no-recording promise stays. Every guest gets an offer of a teardown.

    Practice leaders buy from peers they trust. A small, regular dinner series becomes a known room in each ecosystem, and the notes extend its reach without breaking confidentiality.

    Risks and how to handle them

    • High cost per lead

      Invite only qualified firms and track pipeline per dinner.

    Builds on

    Evidence

    • Your websiteEvent pages still live after the events: the SAP webinar "Where SAP Implementations Lose Margin Before Configuration Starts" (October 7, 2026; "The recording will be emailed to all registered participants"); "Meet us at SuiteWorld" (October 25–28, 2026), covering "Auctor in the NetSuite ecosystem" with Bring IT, Myers Holum and Softype and the offer "Bring us your hardest implementation problem"; a Dreamforce 5K on September 15; and "Full Context at Knowledge 26", an invitation-only dinner in ServiceNow's conference week on May 4, 2026, "third in the series, after Chicago and New York".Source
    • HiringOpen roles (Ashby, November 9, 2026): 11, all on-site in New York: six in engineering (including Forward Deployed Engineer and Software Engineer, Applied AI), two in product, a Founding Account Executive, a Customer Success Manager and a Deployment Strategist; no marketing role.Source
  • 17

    Auctor generates "About 40 discovery questions in 30 seconds" for Softype and drafts SOWs, scopes and designs. The SAP webinar was about Fit-to-Standard decisions and change requests. These artifacts are what consultants search for: "NetSuite discovery questionnaire", "SAP Fit-to-Standard template", "ServiceNow requirements template". Auctor has no templates or downloads on its site.

    High impactMedium effort First result in 2 months Forward Deployed Engineer

    First action

    Publish the NetSuite discovery questionnaire with Softype's permission and credit.

    How to measure it

    Demos from template pages

    Now
    –
    Target
    8 a month
    By
    2 quarters

    Steps

    1. 1

      Pick 12 templates

      Four artifacts by three ecosystems.

      Deployment Strategist 1 day

    2. 2

      Generate drafts

      In Auctor from a sample project.

      Forward Deployed Engineer 1 week

    3. 3

      Practitioner review

      Credited customer experts.

      Customer Success Manager 2 weeks

    4. 4

      Build the library

      /templates, ungated, one page each.

      Software Engineer 1 week

    5. 5

      Add the product link

      "Fill this from your next call" CTA.

      Product Manager 1 day

    6. 6

      Publish weekly

      One new template a week.

      Forward Deployed Engineer weekly

    First result
    2 months
    Cost
    Staff time
    Owner
    Forward Deployed Engineer

    Smallest test

    Publish one NetSuite template and share it on LinkedIn.

    Why it works

    Publish an ungated template library: one discovery questionnaire, one SOW outline and one requirements traceability matrix per ecosystem, each generated with Auctor and reviewed by a customer practitioner who is credited. Every template page shows how Auctor would fill it from a live call and offers a teardown. Add one new template a week.

    Templates draw the exact consultants Auctor sells to and show the product's output before the demo. Credited practitioners share them inside their own ecosystem.

    Risks and how to handle them

    • Giving away what Auctor sells

      The template is static; the product fills, traces and updates it, so the gap is the pitch.

    Evidence

    • Your websiteSoftype case study (a NetSuite-only consultancy): "$2–3M in client opportunities quoted (YTD)"; RFP turnaround cut from "~2–3 weeks to 1–2 days"; RFP team from 2–3 people to 1; "About 40 discovery questions generated in 30 seconds"; the founder: "Having Auctor feels like having a few extra people working on these tasks with great ease and consistency."Source
    • Your websiteEvent pages still live after the events: the SAP webinar "Where SAP Implementations Lose Margin Before Configuration Starts" (October 7, 2026; "The recording will be emailed to all registered participants"); "Meet us at SuiteWorld" (October 25–28, 2026), covering "Auctor in the NetSuite ecosystem" with Bring IT, Myers Holum and Softype and the offer "Bring us your hardest implementation problem"; a Dreamforce 5K on September 15; and "Full Context at Knowledge 26", an invitation-only dinner in ServiceNow's conference week on May 4, 2026, "third in the series, after Chicago and New York".Source
    • Your websiteSitemap (52 URLs, checked November 9, 2026): event pages for Workday Rising (three), Dreamforce (three), SuiteWorld (two), ServiceNow Knowledge 26 and an SAP webinar; two integration pages (/hubspot-integration, /slack-integration); customer stories and partner posts filed under /blog; six /workflow pages; no ecosystem, comparison, pricing, integrations-directory or changelog pages.Source
  • 18

    The new Founding Product Operations Manager will "Own how customer feedback gets captured" from deployment, sales and Slack. Auctor ships often (connectors, Routines, the customer portal), but the site has no changelog or public roadmap. Customers who ask for a feature can't see that it shipped, and prospects can't see the pace.

    Medium impactLow effort First result in 1 month Founding Product Operations M…

    First action

    List what shipped in the last 90 days.

    How to measure it

    Closed-loop feedback rate

    Now
    –
    Target
    90%
    By
    1 quarter

    Steps

    1. 1

      Backfill 90 days

      Shipped items by workflow.

      Founding Product Operations Manager 2 days

    2. 2

      Tag requests

      Link feedback to shipped items.

      Founding Product Operations Manager 1 week

    3. 3

      Build the page

      /changelog with RSS.

      Software Engineer 2 days

    4. 4

      In-app link

      "What's new" in the app.

      Senior Software Engineer, Product 2 days

    5. 5

      Notify requesters

      Email on ship.

      Founding Product Operations Manager ongoing

    6. 6

      Publish monthly

      With the newsletter.

      Founding Product Operations Manager monthly

    First result
    1 month
    Cost
    $0
    Owner
    Founding Product Operations Manager

    Smallest test

    Publish one month's changelog and email the requesters.

    Why it works

    Start a monthly changelog at /changelog: each entry says what shipped, which workflow it improves and, with permission, which customer asked for it ("requested by a NetSuite partner"). Link from the app, the newsletter and the ecosystem pages. Close the loop by emailing each requester when their item ships.

    Visible shipping pace reassures buyers about a young vendor. Crediting requests makes customers feel heard, which helps retention and referrals.

    Risks and how to handle them

    • Reveals the roadmap to rivals

      Publish what shipped, not what's planned.

    Evidence

    • HiringProduct hiring: a Founding Product Operations Manager to "Own how customer feedback gets captured—synthesizing requests and sentiment from deployment, sales, and Slack", and a Product Manager to "deeply understand the workflows of enterprise implementation teams".Source
    • Your websiteSitemap (52 URLs, checked November 9, 2026): event pages for Workday Rising (three), Dreamforce (three), SuiteWorld (two), ServiceNow Knowledge 26 and an SAP webinar; two integration pages (/hubspot-integration, /slack-integration); customer stories and partner posts filed under /blog; six /workflow pages; no ecosystem, comparison, pricing, integrations-directory or changelog pages.Source
  • 19

    Auctor has no pricing page; "Book a Demo" is the only way in. Rocketlane offers a free trial. Emerging SIs, one of the AE's three target segments, often can't justify a long evaluation without knowing the rough cost. Sequoia describes a pilot request that came before the demo, which shows pilots are how this market buys.

    Medium impactLow effort First result in 1 month Founder

    First action

    Write the pilot terms: scope, fee, success criteria, credit.

    How to measure it

    Demo-to-pilot cycle time

    Now
    –
    Target
    -30%
    By
    2 quarters

    Steps

    1. 1

      Define the pilot

      One project, 30 days, fixed fee, credited.

      Founder (go-to-market) 2 days

    2. 2

      Set success criteria

      Artifacts, hours saved, drift caught.

      Customer Success Manager 1 day

    3. 3

      Write the pricing page

      Model, small-firm entry point, enterprise CTA.

      Founder (go-to-market) 2 days

    4. 4

      Publish

      Link from nav and demo page.

      Software Engineer 1 day

    5. 5

      Use in deals

      Offer the pilot after the first demo.

      Founding Account Executive ongoing

    6. 6

      Review

      Pilot-to-contract rate.

      Founder (go-to-market) monthly

    First result
    1 month
    Cost
    $0
    Owner
    Founder (go to market)

    Smallest test

    Offer the fixed pilot in the next five deals before publishing anything.

    Why it works

    Publish a pricing page that explains the model (per seat, per project or platform fee) and the starting point for small firms. Pair it with a named offer: a fixed-fee, 30-day pilot on one live project, with week-one setup by the Deployment Strategist, a capture test and an ROI readout at the end, credited against the first year. Enterprise stays "talk to us".

    A clear entry price and a bounded pilot shorten small and mid-market deals and screen out poor fits before they take AE time.

    Risks and how to handle them

    • Anchors enterprise prices too low

      Publish the model and a small-firm entry point only.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): H1 "One System, Every Implementation"; 14 customer logos including NTT DATA, Myers-Holum, CoreX, Bring IT, Softype, Valiantys and ServiceRocket; investor logos Sequoia, Y Combinator, M12, HubSpot Ventures, Workday Ventures and OneStream; four testimonials but no quantified results; "Book a Demo" is the only way in; no pricing.Source
    • Competitor researchRivals' own homepages: Rocketlane, "Deliver radical efficiency with an agentic, all-in-one PSA", whose Nitro agents "auto-generate project plans" from SOWs, emails and calls, with a free trial; Kantata, a "Professional Services Automation Platform" whose AI "learns how your firm delivers its best work", for mid-market and enterprise services firms.Source
    • PressSequoia's partnership post: "For every dollar spent on software, six are spent on services"; about 9 million implementation consultants across the top 10 software ecosystems account for over $500 billion a year in labor, growing over 10% a year; a pilot was requested by the C-suite of a major enterprise platform.Source
    • HiringFounding Account Executive (New York, posted February 6, 2026): "Own the sales process from prospecting to close, targeting emerging, mid-market, and enterprise Systems Integrators", running discovery and demos for technical audiences without a Sales Engineer on every call; Auctor automates work that "powers $400B+ in services work".Source

Big bets 3

Larger plays that can change the trajectory.

  • 21

    Auctor's round includes Workday Ventures, HubSpot Ventures, M12 (Microsoft's fund) and OneStream, and OneStream is also a customer logo. Each of these platforms depends on its partner ecosystem to implement well. Sequoia notes a pilot was requested by the C-suite of a major enterprise platform. Investors open doors, but a structured co-sell program turns that into pipeline.

    High impactHigh effort First result in 2 quarters Founder

    First action

    Ask the OneStream contact for an introduction to its partner program lead.

    How to measure it

    Vendor-channel opportunities

    Now
    –
    Target
    15
    By
    3 quarters

    Steps

    1. 1

      Map programs

      Partner program, marketplace and owner at each investor ecosystem.

      Founder (go-to-market) 1 week

    2. 2

      Start with OneStream

      Joint proposal with the partner team.

      Founder (go-to-market) 1 month

    3. 3

      Build the partner offer

      Pilot terms for the vendor's SIs.

      Founding Account Executive 2 weeks

    4. 4

      List where possible

      Marketplace listings and certifications.

      Senior Software Engineer, Backend 1 quarter

    5. 5

      Run a joint webinar

      Implementation quality for that ecosystem.

      Founder (go-to-market) 1 quarter

    6. 6

      Extend

      Workday, then Microsoft and HubSpot.

      Founder (go-to-market) 2 quarters

    First result
    2 quarters
    Cost
    Founder time plus listing fees
    Owner
    Founder (go to market)

    Smallest test

    One joint session with OneStream's partner team.

    Why it works

    For each investor ecosystem, propose a partner-program play: Auctor offered to the vendor's implementation partners as a way to raise delivery quality, with joint content ("implementation quality" webinars), a listing in the vendor's partner marketplace where one exists, and a referral path from the vendor's partner team. Start with OneStream, where Auctor already has a customer relationship, and measure partner sign-ups from the vendor channel.

    Vendors care about implementation quality because failed projects hurt their renewals. One vendor partnership can reach hundreds of SIs that a single AE never would.

    Risks and how to handle them

    • Vendors move slowly

      Run one ecosystem at a time with a named sponsor.

    • Being seen as one vendor's tool

      Keep the ecosystem pages neutral and multi-platform.

    Builds on

    Evidence

    • Your websiteSeries A page: "We've raised $20 million to build the first AI-native system of action for implementation teams", led by Sequoia with Y Combinator, M12, Workday Ventures, HubSpot Ventures, OneStream, Tercera and Dig Ventures; teams see "up to 80% efficiency gains across phases like discovery and design". Covered by Axios and Forbes on April 15, 2026.Source
    • PressSequoia's partnership post: "For every dollar spent on software, six are spent on services"; about 9 million implementation consultants across the top 10 software ecosystems account for over $500 billion a year in labor, growing over 10% a year; a pilot was requested by the C-suite of a major enterprise platform.Source
    • Your websiteHomepage (checked November 9, 2026): H1 "One System, Every Implementation"; 14 customer logos including NTT DATA, Myers-Holum, CoreX, Bring IT, Softype, Valiantys and ServiceRocket; investor logos Sequoia, Y Combinator, M12, HubSpot Ventures, Workday Ventures and OneStream; four testimonials but no quantified results; "Book a Demo" is the only way in; no pricing.Source
  • 22

    Auctor's Routines check every new request against the SOW and flag drift, and its traceability links each decision to who made it and when. Across many SIs and ecosystems that is unique data: how often scope drifts, in which phase, and by how much. Sequoia frames the market as $500 billion a year in implementation labor. Nobody publishes hard numbers on where that labor is lost.

    High impactHigh effort First result in 3 quarters Product Manager

    First action

    Add a data-sharing opt-in to the customer agreement for new and renewing accounts.

    How to measure it

    Benchmark sign-ups from target firms

    Now
    –
    Target
    300
    By
    3 quarters

    Steps

    1. 1

      Consent

      Opt-in terms and aggregation rules with counsel.

      Founder (go-to-market) 1 month

    2. 2

      Define metrics

      Drift rate, phase, decision-to-artifact time.

      Product Manager 2 weeks

    3. 3

      Build the pipeline

      Aggregated, minimum group sizes.

      Software Engineer, Applied AI 1 month

    4. 4

      Analyze

      By ecosystem and firm size.

      Product Manager 1 month

    5. 5

      Add practitioner commentary

      Customer practice leaders.

      Customer Success Manager 2 weeks

    6. 6

      Launch

      At a major ecosystem conference, with the benchmark tool.

      Founder (go-to-market) 1 week

    First result
    3 quarters
    Cost
    A quarter of product and engineering time, plus design
    Owner
    Product Manager

    Smallest test

    Analyze drift across ten consenting projects and publish one chart.

    Why it works

    With opt-in consent and strict aggregation (no customer or client identifiable), publish an annual report: drift rate by ecosystem and phase, the share of changes that trace back to unclear discovery, and time from decision to artifact. Pair it with commentary from customer practice leaders and a free benchmark where a firm can compare its own projects. Launch it at the biggest ecosystem conference of the year.

    Original data earns press, analyst and partner attention that a startup can't buy. It also positions Auctor as the authority on implementation quality.

    Risks and how to handle them

    • Customers fear exposure

      Opt-in only, minimum group sizes, review by participating firms before release.

    • Too little data

      Publish a smaller first edition as a "field study".

    Builds on

    Evidence

    • Your websiteWorkflow and delivery pages: "Defensible Backlog" shows a Routine that checks each new request against the Statement of Work and flags drift, with no video and no figures; the /delivery page ("The handoff shouldn't reset the engagement.") sets Auctor against general-purpose AI tools and links the ServiceRocket story.Source
    • PressSequoia's partnership post: "For every dollar spent on software, six are spent on services"; about 9 million implementation consultants across the top 10 software ecosystems account for over $500 billion a year in labor, growing over 10% a year; a pilot was requested by the C-suite of a major enterprise platform.Source
    • Your websiteProduct page: Capture, Contextualize, Create; features include "Proof of performance", "Trace every requirement", "Draft smarter with AI" (first drafts of SOWs, scopes and designs) and "Standardize every implementation"; 19 integrations listed, among them Salesforce, Gong, HubSpot, Certinia, Jira, Confluence, Azure DevOps, Linear, Rally, Slack, Microsoft Teams and Zoom; the page names none of NetSuite, Workday, SAP or ServiceNow.Source
  • 23

    Auctor sells to SIs, but software vendors run large implementation teams of their own. Sequoia's post says a pilot was requested by the C-suite of a major enterprise platform. OneStream is both an investor and a customer logo, and Valiantys and ServiceRocket sit close to vendor ecosystems. Vendor services teams have the same discovery, scope and handoff problems, larger budgets, and a direct stake in product adoption.

    High impactHigh effort First result in 2 quarters Founder

    First action

    Write a one-page vendor-services proposal and take it to the OneStream relationship.

    How to measure it

    Vendor services pilots

    Now
    –
    Target
    2
    By
    3 quarters

    Steps

    1. 1

      Interview vendors

      Five services leaders at software vendors.

      Product Manager 1 month

    2. 2

      Package the offer

      Templates, traceability, product-feedback feed.

      Product Manager 1 month

    3. 3

      Pick two pilots

      From investor and customer relationships.

      Founder (go-to-market) 1 month

    4. 4

      Deploy

      Forward Deployed Engineer on site.

      Forward Deployed Engineer 1 quarter

    5. 5

      Measure

      Time to first artifact, drift, adoption.

      Customer Success Manager 1 quarter

    6. 6

      Decide

      Hire a vendor-focused AE or stop.

      Founder (go-to-market) 1 week

    First result
    2 quarters
    Cost
    Two quarters of founder and Forward Deployed Engineer time
    Owner
    Founder (go to market)

    Smallest test

    One discovery workshop with a vendor services team using Auctor.

    Why it works

    Package Auctor for vendor services organizations: methodology templates for the vendor's own product, traceability from sales engineering into delivery, and a feed of implementation insights back to the vendor's product team. Run two paid pilots with vendors (starting from investor and customer relationships), publish one story, then decide whether to staff a vendor-focused AE.

    Vendor services teams are concentrated, well-funded buyers, and winning them also opens a path to their partner ecosystems.

    Risks and how to handle them

    • Channel conflict with SI customers

      Present it as raising ecosystem quality; keep SI data fully separate.

    • Long enterprise cycles

      Start with paid pilots of fixed scope.

    Builds on

    Evidence

    • PressSequoia's partnership post: "For every dollar spent on software, six are spent on services"; about 9 million implementation consultants across the top 10 software ecosystems account for over $500 billion a year in labor, growing over 10% a year; a pilot was requested by the C-suite of a major enterprise platform.Source
    • Your websiteSeries A page: "We've raised $20 million to build the first AI-native system of action for implementation teams", led by Sequoia with Y Combinator, M12, Workday Ventures, HubSpot Ventures, OneStream, Tercera and Dig Ventures; teams see "up to 80% efficiency gains across phases like discovery and design". Covered by Axios and Forbes on April 15, 2026.Source
    • HiringOpen roles (Ashby, November 9, 2026): 11, all on-site in New York: six in engineering (including Forward Deployed Engineer and Software Engineer, Applied AI), two in product, a Founding Account Executive, a Customer Success Manager and a Deployment Strategist; no marketing role.Source

Wildcards 1

Unexpected experiments, each with a cheap way to test it.

  • 20

    Auctor has a customer portal ("The Customer Portal That Ends the Two Versions of the Truth") where an SI's own clients see decisions and approvals. Those clients include the software vendors' customers and, often, other implementation partners and internal IT teams. Each portal is seen by people who run or buy implementations, and none of them learns the tool's name.

    Medium impactMedium effort First result in 1 quarter Product Manager

    First action

    Ask five portal-using customers whether they'd turn it on, and for what credit.

    How to measure it

    Portal-sourced demos

    Now
    –
    Target
    3 a month
    By
    2 quarters

    Steps

    1. 1

      Ask customers

      Willingness and the credit needed.

      Customer Success Manager 1 week

    2. 2

      Design the line

      Discreet, SI branding first.

      Product Manager 1 week

    3. 3

      Build the setting

      Off by default, account-level opt-in.

      Senior Software Engineer, Product 1 week

    4. 4

      Landing page

      For implementation leaders who saw a portal.

      Software Engineer 2 days

    5. 5

      Launch with volunteers

      Five accounts.

      Customer Success Manager 1 month

    6. 6

      Measure

      Clicks and demos per portal.

      Product Manager monthly

    First result
    1 quarter
    Cost
    Engineering time and small credits
    Owner
    Product Manager

    Smallest test

    Turn it on for two volunteering customers for a month.

    Why it works

    Add an optional, discreet "Powered by Auctor" line to portal pages and approval emails. Offer SIs a small credit for turning it on. The link goes to a page for implementation leaders ("Your partner runs this project on Auctor") with a teardown offer. Also track which client-side viewers later run their own projects with other partners.

    Product-led exposure to exactly the right audience at near-zero cost, and the line signals rigor on the SI's behalf.

    Risks and how to handle them

    • SIs want the portal to look like their own

      Keep it opt-in, small and below the SI's brand.

    Evidence

    • Your websiteBook-a-demo page: the heading "Book a Demo" and ten customer logos, with no testimonials, figures, video, product tour or sandbox. Resources page: press, 12 blog posts (including "The Customer Portal That Ends the Two Versions of the Truth"), 8 case studies and 6 workflow pages; no newsletter signup and no webinar library; the footer link labelled "Case Studies" goes to /resources.Source
    • Your websiteProduct page: Capture, Contextualize, Create; features include "Proof of performance", "Trace every requirement", "Draft smarter with AI" (first drafts of SOWs, scopes and designs) and "Standardize every implementation"; 19 integrations listed, among them Salesforce, Gong, HubSpot, Certinia, Jira, Confluence, Azure DevOps, Linear, Rally, Slack, Microsoft Teams and Zoom; the page names none of NetSuite, Workday, SAP or ServiceNow.Source

03

How Programmable can help

Where an idea in this playbook is something Programmable builds or runs, it's listed here with what we'd do. Everything else is yours to run.

ProgrammableTalk

Fill the events in this plan

These ideas are events. Talk gets registrants for them and tells you who's coming and what their company does before the day.

Plan an event (opens programmable.talk in a new tab)
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • HighlightTA growth strategyAn on-demand talent acquisition team: embedded talent partners (IntegrateTA), a fully outsourced recruiting function (FunctionTA), one-off…21 growth ideas
  • Power Digital growth strategyA growth marketing agency organised in vertical divisions (B2B, Consumer Services, CPG, Fashion, Healthcare via Cardinal, Lifestyle) with…21 growth ideas
  • Parker growth strategyAn AI creative strategist for paid social: it researches a brand's reviews, competitors, TikTok, Reddit and ad performance, then answers…21 growth ideas
  • Swayable growth strategyA causal AI platform for creative pre-testing: randomized controlled trials with real respondents measure how ads, messaging, packaging…21 growth ideas
  • aosu growth strategyA direct-to-consumer smart home security brand selling solar and battery security cameras, video doorbells, indoor cameras and…22 growth ideas
  • Astronomer growth strategyThe company behind Astro, a managed orchestration platform for data and AI powered by Apache Airflow, with Astro Private Cloud, Astro…21 growth ideas
  • InLoop Robotics growth strategyInLoop builds and rents Loop V1, a two-armed robot system for warehouse work (box assembly, kitting, visual inspection, content…23 growth ideas
  • Evergreen Nephrology growth strategyValue-based kidney care: care teams (nurses, care coordinators, social workers, dietitians) that support patients with chronic and…22 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 9, 2026, and cites them throughout. Auctor did not commission, review or endorse it, and Programmable is not affiliated with Auctor. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Auctor runs its business.

Something wrong, or do you represent Auctor? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 306 ideas

    Ecosystem pages from the expired event pages, a named result on every story, story cleanup, the SAP recording, walkthrough videos and a newsletter.

  2. Days 31 to 6010 ideas

    Demo form routing, integration pages, the capture test, the always-on teardown, quarterly ROI reports, time to first artifact, referrals, the template library, a changelog and a published pilot offer.

  3. Days 61 to 907 ideas

    "Auctor and your PSA" pages, delivery-team expansion, monthly dinners, the client-portal loop, and commitment to the big bets: ecosystem co-sell, the Scope Drift report and vendor services teams.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value RFPs and SOWs in minutes or days instead of weeks. The most cited problem: context lost between discovery sessions and handoffs.

  • Delivering more without adding headcount
  • Scope drift against the SOW
  • In their words: “discovery”

Market

Competitive landscape

3 competitors compared: Rocketlane, Kantata and General-purpose AI assistants and meeting notetakers.

  • Gap to exploit: Ecosystem-specific AI for NetSuite, ServiceNow, SAP and Workday partners
  • Rocketlane: Built around project and resource management, not pre-sales discovery and traceability
  • Kantata: Focused on resourcing and finance more than implementation artifacts

Hiring signals

Auctor is hiring 11 people, all on-site in New York, and the mix shows a company moving from founder-led sales to a repeatable motion.

  • Founding Account Executive: Selling to emerging, mid-market and enterprise SIs without a sales engineer. Ideas 1, 7, 15, 19.
  • Customer Success Manager: ROI narratives from sessions, artifacts and active users; QBRs and renewals. Ideas 2, 12, 14.
  • Deployment Strategist: Configures agents to each customer's methodology. Ideas 11, 13.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks first (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence