Every engagement
is shaped before
it starts.
Every engagement is different. We do not run a fixed playbook. What is fixed is that the shape of the work (scope, methodology, cadence, decision rights, change control, handoff) is agreed in writing before kickoff. NYC government engagements run through RFP and Statement of Work; private-sector engagements run through a problem statement and engagement brief. This page describes both routes and what we commit to once the work is shaped.
Three phases.
Shape varies.
Discovery.
Length varies with the system and the question. We map the system as it is, interview the people who actually use it, document the constraints, and write a scope of work your procurement team can defend. Discovery ends with a written brief and a go / no-go decision. We have walked away from engagements at this stage; that is the point.
Build.
Senior practitioners staff the engagement end to end. Methodology, cadence, and review structure are agreed in the Statement of Work or engagement brief and run on your calendar, not ours. Scope changes are documented, estimated, and signed off before work begins. Code, tests, infrastructure, and documentation are the deliverables; not status reports.
Handoff.
The handoff is real. We document the system well enough that your engineers can extend it without us in the room, run knowledge-transfer sessions with the people who will own it, and we leave. No parked retainers. If you need ongoing support afterwards, that is a separate engagement on its own terms.
How the
shape gets agreed.
NYC government engagements: RFP to Statement of Work.
Most of our NYC engagements run through formal procurement. We respond to your RFP, and the Statement of Work that follows is where the engagement gets defined: scope, methodology, governance, meeting and status cadence, decision rights, change control, deliverables, and what handoff looks like. The SOW is what both sides hold each other to. If your contracting vehicle requires a different form (task order, MOU, contract amendment), we adapt to it; the substance is the same.
Private-sector engagements: problem statement to engagement brief.
Private-sector engagements typically start with a problem statement from you and a procurement-grade brief from us in response: scope, deliverables, engagement boundaries, methodology, cadence, and a proposed shape for the work. The brief becomes the engagement contract, signed under your paper. The mechanics differ from the SOW route; the substance is the same.
We choose methodology
with you.
Methodology is a choice we make with you, not a default we impose. We work in four shapes; the right shape follows the regulatory environment, the deliverable's nature, your team's posture, and how change will be handled. The choice gets written into the SOW or engagement brief.
Agile.
Lean.
Waterfall.
Hybrid.
Who decides what.
You decide.
Scope. Budget. Deadlines. Acceptance criteria. Production deployments and rollbacks. Anything regulatory or contractual. Our job is to make those decisions easier to make, not to make them for you.
We decide.
Technology choices inside the agreed architecture. Implementation patterns. Code-review discipline. How we structure our own team. We will tell you what we picked and why, and you can override us; the default is that we own these.
We decide together.
Architectural trade-offs. Scope changes mid-engagement. When to embed our people in your team versus run as a standalone project. These get worked through the agreed review forums, not in side channels.
Scope changes
are normal.
Every serious engagement runs into scope changes. The signal of a healthy engagement is not the absence of change, it is whether the change gets handled in writing and signed off before work begins.
Our process: any change to scope, timeline, or budget is documented as a short change note. We estimate the impact. The named decision-maker signs off. Work begins. The change note becomes part of the engagement record.
No surprises in the final invoice. Procurement reads the change-note record at audit time and finds a complete trail.
We leave clean.
Documentation, knowledge transfer, and team training are deliverables, not optional extras. The team that built it sits with the team that will own it until your people can extend the system without us in the room.
After handoff, we leave. We do not park retainers, run perpetual maintenance contracts, or condition the value of the work on future invoices. If you need us back for a discrete piece of work later, that is a separate engagement with its own brief.
Year two looks like: your engineers extending the system. Audit response running against the documented query paths we wrote together. Your operations team running the runbooks we left behind.
What buyers usually ask
How do you handle our RFP and Statement of Work process?
We respond to your RFP in your prescribed format and against your evaluation criteria. The SOW that follows the award is what we work from. We expect the SOW to specify scope, methodology, governance, meeting and status cadence, decision rights, change control, deliverables, and handoff conditions; if your standard template leaves any of those open, we will propose specific language in writing before signature.
Which methodology will you use on our engagement?
Agreed with you, written into the SOW or engagement brief, not assumed. We work in Agile, Lean, Waterfall, or Hybrid; the choice follows the regulatory environment, the deliverable shape, your team's posture, and how change will be handled. If you have a required methodology under your procurement vehicle, we adopt it.
Can we use our project-management tools?
Yes. We adapt to your tools and process rather than imposing ours. If you run on Jira, we run on Jira. If you live in Linear, GitHub, ServiceNow, or a custom workflow, we live there too. The only line we hold is on engineering discipline; everything else flexes to your environment.
Do you sign our paper or yours?
Yours. We have worked under enough contract vehicles, master service agreements, and procurement frameworks to be comfortable adapting to your contracting standards. We will flag any clause our delivery team cannot defend before signing; everything else is in scope.
What happens if you cannot complete the engagement?
We document continuity plans at kickoff: which roles are critical, how we would staff a replacement, what artifacts the engagement would leave behind even mid-build. Our extended bench means we have rarely had to invoke it; the plan exists so that buyers do not have to ask.
Can you embed in our existing team?
Yes. Team augmentation is one of our three engagement models. Embedded practitioners follow your team's process, attend your standups, and report through your existing chain of command. We retain quality discipline on the work but do not impose process on your team.
What does kickoff look like?
A working session with your named decision-maker and the internal SMEs we need access to. We confirm the scope of work and acceptance criteria, lock the methodology, cadence, and escalation paths agreed in the SOW or engagement brief, set the change-note process, and write the kickoff brief. Once kickoff is signed, both sides have the same document open.
Ready to talk
about an engagement?
Send us a problem statement. We typically respond within a week with a procurement-grade brief. If you have an open RFP, we are set up to respond against it.
letscreate@nuarch.com