The development bench for Sage partners
Your client needs something Sage does not do. You do not have developers on staff, or they are booked. We scope it, build it and support it, and you keep the client.
- Fixed-price quotes you can pass on
- Previewed on your client's data
- Sage-certified consultants who write code
Through you, by referral, or under your brand
The arrangement is chosen per project. Much of our work arrives through Sage partners, most of it in one of the first two ways.
Through you
You hold the contract and the relationship. We work under your project manager, to your templates, and issues are reported through you. Your client sees one team.
By referral
You make the introduction and step back. We contract with the client directly for the build, and you stay the Sage partner of record for licences and implementation.
Under your brand
A build or one of our tools delivered with your name on it. The software is the same. The branding and packaging are yours.
Software vendors, too
Do you make a field service, payroll or operations app whose customers keep asking for a Sage connector? We build the connector to Sage Intacct, Sage 100 Contractor or Sage 300, keep it working when either side updates, and help your customers get it running. Pricing is agreed with each vendor.
The requests that sit in a consultant's inbox
If it reads like one of these, it is probably a small, fixed-price build.
Data that has to leave Sage on a schedule
A Sage 300 group that owes corporate a trial balance feed every month, in a format someone else dictates.
An approval step Sage does not have
An Intacct client that wants project managers to approve invoices before accounting posts them.
A field app that does not talk to Sage
A contractor on Sage 100 Contractor whose office types every job from the field app into work orders.
A migration bigger than the templates
A move into Sage Intacct with more history and more rejected rows than import templates can take.
A utility that saves your consultants hours
A repetitive setup job across companies, users or modules that should be one run instead of an afternoon of clicking.
A customization nobody can maintain
A custom program with no source code and no developer, blocking an upgrade.
Built so you can quote it and hand it over
We have been consultants on the other side of this, so the work arrives the way a partner needs it.
- A price before a promise. Itemized scope and one number. Budgetary figures are labelled as such, with a firm quote to follow.
- A preview on real data. Your client sees it run on their own data before it goes live.
- Honest scoping. If the answer is a Sage setting and not a build, we say so, even when it costs us the job.
- A proper handover. Install guide, documentation, a 30-day defect warranty and support after go-live.
Three Sage products and the plumbing around them
Sage Intacct
- Web Services API integrations
- Approval and workflow apps
- Imports, bulk edits, migrations
Sage 100 Contractor
- Direct SQL Server reads and writes
- Field service and operations sync
- Reports, utilities, data moves
Sage 300
- Sage 300 .NET API posting
- Multi-company extracts by SFTP
- Security and admin utilities
What partners ask first
Who owns the client relationship?
You do. When we work through you, your project manager runs the engagement and issues are reported through you. On a referral we contract with the client for the build only.
How is the work priced?
At a fixed price against an itemized scope, quoted before anything starts. Where the scope is not clear yet, we quote a short discovery step first and a firm price after it. You always have a number you can put in front of your client. When we work through you, we quote you, and you set your client's price.
Who owns the code?
That is agreed per project, in writing, before the work starts. Some builds transfer to the partner or the client on final payment. Others stay ours and are licensed, usually when they start from one of our own tools.
What happens after go-live?
Builds come with an install guide, documentation and a 30-day defect warranty. After that we offer support and maintenance, because an integration has to keep working when Sage or the other system is updated.
Can a build run under our own brand?
Yes. A build, or one of our own tools, can be delivered white label under your name. The software is the same. The branding, naming and packaging are yours.
Will you compete with us for the client?
No. On work you refer or subcontract to us, we stay in our lane: the build, its documentation and its support. The client's Sage licences and implementation work stay with you.
Have a client request sitting in your inbox?
Send it over. We reply within one business day and tell you whether it is a build, a setting or neither.
