No. About half of our engagements are net-new NetSuite implementations and about half are optimization, rescue, customization, integration, or managed support work for clients already on the platform. We are often brought in after a previous implementation has stalled, gone over budget, or failed to deliver the original business case.

Yes. We frequently partner with internal NetSuite administrators and finance system teams. A capable internal admin makes implementations and optimizations measurably more successful, and we structure engagements to build internal capability rather than replace it.

Both, depending on the engagement. Implementations and well-scoped customization projects are usually fixed fee against a detailed Solution Design Document. Optimization, integration, and managed support work is often time-and-materials against a defined service level.

Every project has a documented change control process. New requirements identified during discovery or build are logged, scoped, and either incorporated into the current phase or deferred to a follow-on phase. This is how we avoid scope creep, which industry analysts consistently identify as the leading reason NetSuite projects go over budget.

Only where it is the right answer. Over-customization is one of the most common, most expensive mistakes in NetSuite. We will push back when a customization request would be better solved by a process change or by using native NetSuite functionality. That posture is a feature, not a bug.

We accept fixed deadlines when they are realistic for the scope. We do not accept fixed deadlines for projects whose scope would require shortcuts in discovery, data migration, testing, or training to hit them.