NetSuite practice

What sales agreed to is what finance bills.

We implement and connect NetSuite for publishers, broadcasters, and B2B media companies. The ledger is where a deal becomes revenue, and most of the pain between a closed deal and a collected invoice lives in the handoffs into it. We build those handoffs so they hold.

  • Order to cash, billing, and revenue recognition
  • Connected to HubSpot, Salesforce, Naviga, and the ad stack
  • Finance-grade reconciliation, not a nightly CSV

When teams call us

Eight reasons a NetSuite conversation starts.

You’ll recognize at least one.

  1. 01

    Month end is a nightmare. Delivered against booked, reconciled by hand, on rules that live with one or two people.

  2. 02

    Sales closes in the CRM. Finance re-keys it. The same order typed twice, and the two never quite agree.

  3. 03

    Revenue is recognized in a spreadsheet. Campaign schedules, multi-month contracts, and make-goods are tracked outside the ledger and posted by hand.

  4. 04

    AR lives in two places. So nobody can see what a customer is actually worth, or who is quietly late.

  5. 05

    You are outgrowing QuickBooks or Sage. Or an ERP that was built for a business you no longer run.

  6. 06

    The integration is an export somebody runs. When they are out, invoices are late.

  7. 07

    Two acquisitions, three charts of accounts. Consolidation happens in a workbook the week before the board meeting.

  8. 08

    Card fees go unoffset. Quietly costing about three percent of every card payment, because nobody set it up.

None of these are anyone’s fault. All of them are expensive. Most have been true long enough that nobody in the building sees them any more.

What we do in NetSuite

Ten services. One order-to-cash workflow.

Each service is scoped on its own, and each one is designed to sit inside the same connected system with the CRM and the ad stack.

Plan

Know what to build before anything is built.

01 · Strategy

Order-to-cash assessment

A read of how a deal becomes an invoice becomes cash today, across the CRM, the ad system, and the ledger, ending in a plan.

Read more
Build

Implement, migrate, connect, and extend.

02 · Implementation

NetSuite implementation

Financials, order management, billing, and revenue recognition configured for how a media company sells and delivers.

Read more
03 · Migration

Migration to NetSuite

A controlled move from QuickBooks, Sage, or a legacy ERP, with open balances reconciled and history where finance needs it.

Read more
04 · Integration

CRM and ad-system integrations

NetSuite connected to HubSpot or Salesforce, to Naviga or Google Ad Manager, and to the subscription platform, so an order is entered once.

Read more
05 · Revenue workflow

Order to cash

Sales orders, billing schedules, invoicing, revenue recognition, and collections that run from the CRM through NetSuite without re-keying.

Read more
06 · Extension

Custom development

SuiteFlow first, then SuiteScript, custom records, and API work for the parts of the workflow NetSuite cannot configure.

Read more
07 · Reporting

Revenue reporting

Saved searches, dashboards, and analytics that show booked, delivered, billed, recognized, and collected on one set of definitions.

Read more
Run

Keep it working, keep it reconciled, keep improving it.

08 · Managed services

Managed NetSuite

Ongoing administration, release review, integration monitoring, and month-end support from a named team who knows your instance, on a monthly retainer.

Read more
09 · Enablement

Training and adoption

Role-based training for billing, finance, sales ops, and administrators, on your instance, with your transactions.

Read more
10 · Practical AI

AI and automation in NetSuite

Workflow automation and governed assistants for the manual steps in billing, collections, and close, while people keep the decisions.

Read more

Where we work in the platform

The modules, configured as one ledger.

NetSuite sells modules separately. Order to cash does not run separately, so we implement them on one customer and item model with the CRM and the ad system connected.

GL · AR · AP · Close

Financials

Chart of accounts, entities, and the close process, built for consolidation across the properties you own.

Sales orders · Fulfillment · Billing

Order Management

Sales orders created from the CRM, billing schedules that follow the campaign, and invoices that match what was delivered.

Arrangements · Schedules · Make-goods

Revenue Management

Revenue recognized on the dates the contract says, with adjustments handled in the ledger rather than a workbook.

Subscriptions · Usage · Renewals

SuiteBilling

For subscription and usage revenue that belongs in NetSuite, connected to Recurly or Omeda when it does not.

SuiteFlow · SuiteScript · Custom records

SuiteCloud Platform

Where the media-specific model lives: custom records, workflow automation, and the scripts that fill in what configuration cannot.

Saved searches · Workbooks · Warehouse

SuiteAnalytics

Native reporting first, workbooks or a warehouse when the question crosses systems at scale.

Payroll, HR, and inventory-heavy manufacturing modules are outside the practice. We configure what a media company’s revenue operation needs and refer the rest.

How an engagement runs

Five phases. The same five every time.

What changes from engagement to engagement is how long each phase takes, and that is decided by what discovery finds, not by a template.

  1. 01

    Discover

    Map the money as it moves.

    • Interviews with finance, billing, sales ops, and the people who run month-end
    • A read of the instance, the data, and every system that touches an order
    • A written finding: what works, what is manual, what is silently wrong
  2. 02

    Design

    Decide the model before the build.

    • Customer, item, billing, and revenue design that matches how inventory is sold and delivered
    • A chart of accounts and entity structure finance agrees on, in writing
    • Integration architecture and a migration plan with owners and cutover rules
  3. 03

    Build

    Configure first. Code only where it earns its place.

    • Configuration, workflow, and reporting built to the design in a sandbox
    • Migration in controlled loads with reconciliation at each step
    • Integrations built and tested against real orders, not samples
  4. 04

    Enable

    Make it the way the close gets done.

    • A parallel close with the people who will live in it
    • Role-based training: billing, AR, finance, sales ops, administrators
    • A cutover at a period boundary with a rollback and a named decision-maker
  5. 05

    Run

    Stay through the first close, then keep it steady.

    • Stabilization through the first live month-end with fixes shipped as they are found
    • Reviews after the first two closes against the original finding
    • Handoff to your administrator, or managed services if you would rather we keep it

An ERP that agrees with the CRM is not a feature you buy. It is a set of decisions someone has to make, and then build.

How we work

The ledger is the last word. Build toward it.

These are the rules we build by, on the finance side of the workflow as much as the sales side.

The data model comes from the business, not the default.
Agency, advertiser, and bill-to are different things. Campaign, schedule, and make-good are different things. The model has to know.
Configuration before code.
Native features and SuiteFlow first, SuiteScript only when it removes a manual step nothing else can. Less to maintain, less to break in the next release.
Reconciled, not synced.
An integration that moves data is half the job. The other half is proving the two sides agree, every day, in a report someone reads.
Governed automation, human-owned decisions.
Every workflow and every assistant has an owner, a log, and an off switch. Automation moves the work; people make the calls.
Inspectable by design.
Finance should be able to see what the system did and why. Documentation, naming conventions, and change logs are deliverables, not favors.
The people who scope it, build it.
No handoff from a sales engineer to a delivery team you have never met. The person in discovery is the person in the build.

Proof

On the record.

What we can point to publicly. Ask us for the detail behind any of it.

  1. Certified implementation and integration partner. NetSuite is one of four platforms we hold a certification on, alongside HubSpot, Salesforce, and Naviga.

  2. Northstar Travel Group. An enterprise-wide HubSpot CRM foundation across global divisions, with NetSuite ERP integration, proposals, and contract management as the next phase.

  3. Both ends of the workflow. We implement the CRM and the ledger, so the handoff between them is one team’s responsibility rather than a seam between two vendors.

  4. Twenty-three media companies on the wall. National groups, metros, local broadcast, and B2B publishers. Every one of them has an insertion order that has to become a general-ledger entry.

Work and news

Notes from NetSuite engagements.

Case studies from NetSuite engagements are being prepared for publication. The record above is public in the meantime.

Questions we get

Before you ask.

Do you implement NetSuite on its own, or only with a CRM?

On its own when that is the need. Most of our NetSuite work sits between a CRM and the ledger, because that handoff is where media companies lose the most, but a financials implementation or a migration from QuickBooks stands on its own.

How long does an implementation take?

It depends on what discovery finds: entities, modules, systems to connect, data to migrate, and how many teams have to agree on the model. We scope a timeline after discovery, cut over at a period boundary, and hold to it.

What does it cost?

Engagements are either fixed-scope projects or ongoing managed services, and both are priced after discovery, when we know what the work is. A conversation is the right way to get a number. This page is not.

Can NetSuite talk to HubSpot, Salesforce, Naviga, or Google Ad Manager?

Yes, and that connection is the center of most of our NetSuite work. Some of it is connectors. Most of it is built, because ad order systems and CRMs have rules the ledger does not know until someone teaches it, and the reconciliation has to be built alongside.

Who owns the instance when the project ends?

You do. Every engagement ends with documentation, an administrator handoff, and a trained owner on your side. Managed services are available if you would rather we keep running it, but they are never a condition.

Do you do payroll, HR, or manufacturing?

No. We configure what a media company’s revenue operation needs: financials, order management, billing, revenue, and the integrations around them. We refer the rest.

Other platforms

The same practice, in the systems around it.

Most engagements touch more than one of these. The method is the same in each; the handoffs between them are the point.

  • HubSpot

    CRM, marketing, service, and the front of the lead-to-cash workflow.

  • Salesforce

    Sales Cloud and Service Cloud, built, cleaned up, or connected to the systems that bill.

Start with the stuck point

What should the ledger know that it doesn’t?

Bring the handoff, reconciliation, or report that keeps resurfacing. We will tell you whether it is a NetSuite problem, a data problem, or a systems problem, and what to do about it.