Plug-in · Account documentation & action plan

Do you know what your NetSuite account actually does?

Every grown account holds scripts, workflows, fields and roles that somebody built years ago — and whose interplay nobody fully knows any more. SuiteLens reads your account and describes it in plain language: what exists, how it connects, and what a change would touch. And now not only the current state, but what to do about it — with effort, delivery path and blast radius for every finding.

Text, not diagrams Updates with the account Beta programme · 3-month minimum With our partner Splotch
Account map · as of today · Sample GmbH
Scripts user events, Suitelets, map/reduce — each with purpose and trigger 212
Workflows states, conditions and actions in plain words 38
Custom records fields, relationships and who writes to them 64
Fields where they are set, read and displayed 1,482
Connections what an object touches — upstream and downstream visible
ALWAYS CURRENT The description comes from the account, not from a Word file written the year before last.
Why

Documentation is out of date the day it is finished.

Almost every NetSuite account tells the same story: there was documentation at the start, then came two projects, three consultants and a change of staff — and today you know that something works, but no longer exactly why.

The knowledge sits in people's heads

Whoever built the account knows why that field exists. Once they are gone, the reason is gone — the code stays.

Nobody reads scripts for fun

Administrators and project managers need to understand what happens without reading SuiteScript. The standard offers nothing for that.

Changes with unknown effect

Rename a field, disable a workflow, adjust a role — what depends on it often shows only when something breaks.

Onboarding takes weeks

New colleagues and external consultants start from scratch every time: click, search, ask. You pay for that twice — internally and by the day rate.

Diagrams age badly

A chart is right on the day it is drawn. After that the account changes and the picture does not — until nobody trusts it any more.

Audits and projects ask

During migrations, audits and takeovers somebody wants to know how processes really run. “A script does that” is not an answer.

What's in it

Descriptions, not picture puzzles.

SuiteLens discovers objects and their connections across the whole account and writes coherent text from them: what a process does end to end, which objects are involved and where it touches other processes.

Question: what depends on custbody_approval_status?
Set by two user event scripts and one workflow on approval 3 places
Read by approval dashboard, saved search “Open purchase orders”, email template 3 places
Displayed on two forms; one role does not see the field forms
If you change it approval, reporting and the notification to approvers are affected impact
BEFORE THE CHANGE The question “what happens if I touch this” is answered before you touch it.
Who it's for

Three roles, three reasons.

Administrators

Fast orientation in a complex account and a reliable source for how configuration and processes actually work together.

Developers

See the upstream and downstream effect of a change, avoid regressions and narrow down errors faster.

Project managers and consultants

Explain processes to the business and to management, onboard new colleagues, document implementations in a way others can follow.

How it runs

Three steps to the first documentation.

1

Install the bundle

The extractor bundle is installed in your account and reads its structure: scripts, workflows, records, fields, roles and how they connect.

2

Let it analyse

The description is produced from that structure — together with our partner Splotch, who specialise in exactly this kind of analysis.

3

Read it and pass it on

You get coherent text instead of an object list — for onboarding, for checking a change or for handing over to a project team.

Beta programme: SuiteLens currently runs with selected customers. €200 per month with a three-month minimum — in return your feedback goes straight into the product and we look at your account together.
From finding to decision

Not just the finding. The way forward.

An analysis that ends with a list of problems only moves the work elsewhere. So every finding comes with a way to resolve it — as an interactive page you can share and comment on with your team, rather than a PDF nobody opens twice.

Effort

Every finding is rated S, M or L. You see at a glance what is a quick fix and what is a project.

Delivery path

The steps that resolve the finding — from analysis through the rebuild to testing in a sandbox account.

Cost frame

Stated separately: what runs automated and where a human has to decide. So it stays clear what the effort is spent on.

Blast radius

Interactive view of what the change touches — upstream and downstream, before you touch anything.

Open questions

Whatever the account alone cannot answer is listed as an open question in the plan — instead of surfacing later as a surprise.

Documentation included

The SuiteLens description of your account is part of it. The plan sits on a documented current state, not on a snapshot.

Recurring, not one-off: the scan runs regularly, not just at project start, so you see what has been added since the last run. Your team gets read access to the analysis — to look things up, comment and request work.
Working together

Three levels. You decide how far.

1

Understand

Recurring scan, documentation and action plan. You get a dependable picture of your account and a list sorted by effort. What comes of it is your call afterwards — with no obligation.

2

Have it delivered

Fourangle implements what you approve — with the same tools the plan came from. You can see what is being worked on at any time and approve every change before it reaches your production account.

3

Run it yourself

If your team wants to work in it permanently — with versioning, approvals and running documentation — we arrange a Splotch licence of your own. We stay available for the NetSuite side.

Partnership

Together with Splotch.

The analysis is built in cooperation with Splotch, Inc. Splotch puts a layer on top of grown ERP and CRM systems: a map of the current state, versioning and approvals for planned changes, and impact analysis before anything reaches production — the same guardrail applies to work carried out automatically. Fourangle brings the NetSuite side: what actually matters in a German finance environment and what to look for when reading an account.

Technical facts

What your IT wants to know up front.

Delivery

SuiteBundle 602065 — installation and updates through NetSuite’s bundle mechanism.

Scope

Scripts, workflows, custom records, fields, forms and roles, including how they connect.

Result

Text descriptions that change with the account — no diagrams anybody has to maintain.

Analysis

An interactive page instead of a PDF: findings with effort, delivery path and blast radius. Your team reads along and comments.

Partner

Analysis together with Splotch, Inc. (splotch.ink).

Programme

Beta, €200 per month, three-month minimum.

Requirements

A NetSuite account with permission to install bundles. No additional module.

FAQ

Frequent questions

What exactly is read?

The structure of your account: scripts, workflows, custom records, fields, forms and roles together with the way they connect. That is what the description is built from. Before anything runs we walk you through what is read and where it goes.

Why text instead of diagrams?

Because diagrams age and nobody maintains them. Text that is regenerated from the account on every run describes the current state — and can be searched, quoted and pasted into a handover.

Does this replace our own documentation?

It replaces the tedious part: taking inventory. The business reasoning you add — why something was built that way — remains yours, but it gets much shorter.

Does it help with concrete changes?

Yes. For an object you see where it is set, read and displayed — in other words what a change would touch, before you make it.

What is new compared to plain documentation?

Documentation describes the current state. What is new is what follows from it: every finding comes with an effort estimate, a delivery path, a cost frame and the blast radius of the change. The result is an interactive page you can share with your team — not a list somebody has to translate first.

Do we have to have you do the work?

No. The action plan is yours and is written so that your own team or another provider can work through it. If you do hand delivery to us, we continue with the same tools the plan came from — and you approve every change before it reaches your production account.

Who is Splotch?

A company specialising in making grown ERP and CRM systems readable. For SuiteLens we work together: Splotch contributes the analysis, Fourangle the NetSuite practice.

Why beta?

Because the product is still growing and we sharpen it on real accounts. Joining now gets you a direct line to us — and a say in what comes next.

What does it cost?

€200 per month with a three-month minimum. Monthly thereafter.

Next step

Let us look into your account.

We clarify up front what is read, and show you the description of an area you know well — that is the fastest way to see whether it is any good.