Co-win the development deals you used to decline for lack of staff
GIIP FDE Box adds AI development, cloud build and operations execution to the customer relationships and sales power an SES firm already has. Not a plain replacement for on-site staff — it turns deals you lost to staff shortages into joint proposals, contract development and managed operations.
For executives and sales leads at SES firms and SES sales companies | For SES sales companies turning away development and infrastructure deals for lack of staff
This is for executives and sales leads at SES firms, SES sales companies and IT-staffing sales companies. It is not about "adding people" — it is about winning the development, infrastructure and operations deals you have been declining, as your own offering.
This is not about adding people — it is about turning the deals you used to decline into your own offering.
- Re-examine deals you declined because you could not secure engineers
- Widen your proposal scope beyond web development to infrastructure, DB, deployment and operations
- The SES partner keeps the customer contact and the customer relationship
- GIIP handles technical review, proposal support, development, build and operations
- Build recurring revenue as a development/operations contract, not a one-off staffing referral
- Negotiate the revenue structure according to the partner's sales and account-management role
At the consultation stage we organize, in advance, the customer proposal scope, GIIP's scope, the partner's role and the assumed revenue structure. We do not over-promise returns; instead we let you confirm revenue, cost and role split before the deal.
A web-rebuild deal with no Java developers
You cannot secure three developers, so a rebuild deal you could have won is let go.
An infra deal with no AWS operator
With no one to assign for build or operations, you have to decline the infrastructure work.
A deal where dev is done but ops will not run
No one can handle incidents or DB tuning, so you cannot touch the maintenance phase.
An on-site-staff commercial flow
On a "we send people" premise, the moment there is no person the deal is lost.
Limits of the man-month model
Revenue is bound to headcount, so deals beyond your capacity cannot be taken.
Shortage of dev/infra/ops talent
Infrastructure and operations talent in particular is scarce — the hardest area to secure.
The SES firm owns customer relationships and sales; GIIP owns technical review, development, infrastructure and operations. Choose from four deal models per deal.
Model A: Reseller partner
The SES firm sells FDE Box to the customer as its own solution and earns a sales/management commission.
Model B: Joint proposal
The SES firm owns the customer relationship and front-line contact; GIIP owns technical review, development, infrastructure and operations.
Model C: Filling the resource gap
Within a deal the SES firm has secured, GIIP supports only the missing development, infrastructure and operations work as a back-end team.
Model D: Shift to contract delivery
Rather than dropping deals that cannot be staffed on-site, redesign them with the customer as remote contract, quasi-delegation or managed-operation work.
| Task | SES partner | GIIP |
|---|---|---|
| Finding customers | Owns | Supports |
| Customer relationship & sales contact | Owns | Joins when needed |
| Requirements confirmation | Joint | Joint |
| Technical fit review | Provides info | Owns |
| Proposal & quote | Joint | Owns the technical part |
| Development & testing | Manages or reviews | Owns |
| Cloud / DB / CI/CD build | Coordinates with customer | Owns |
| Operations & incident analysis | Customer contact | Technical response |
| Deliverable sign-off | Coordinates with customer | Prepares & submits |
The direct-contract party with the customer, whether re-subcontracting is allowed, and the scope of responsibility are decided per deal.
- 1
Receive an anonymized deal sheet with the customer name removed
Partner prep: deal outline, technical requirements and target deadline with the customer name hidden
- 2
GIIP reviews the technical requirements and contract conditions
Partner prep: known constraints and budget expectations
- 3
Reply with feasibility and risk factors
Partner prep: share what the customer is most concerned about
- 4
Decide the role split between the SES partner and GIIP
Partner prep: confirm the sales/contact scope you will own
- 5
Organize the recommended contract form and scope of work
Partner prep: the customer's contracting practice (quasi-delegation / contract feasibility)
- 6
Draft the joint proposal and quote
Partner prep: presentation format and submission deadline for the customer
- 7
A technical lead joins the customer meeting if needed
Partner prep: whether attendance is possible and the role split on the day
- 8
After signing, run development, build and operations
Partner prep: the contact route as the customer's window
- 9
Share progress and deliverables regularly
Partner prep: reporting timing to the customer
!Deals that do not fit as-is
- Deals requiring a named person to be on-site at the customer
- Deals where submitting a specific individual's skill sheet is a contract condition
- Deals premised on the customer directing an individual worker directly
- Deals that are mostly physical on-site equipment work
- Deals that legally require a qualified individual to perform the work in person
- Deals where neither the customer nor the partner has a requirements-approval owner
- Contracts that prohibit re-subcontracting
That said, if the deal can be restructured as contract development, operations support or joint execution, we can review it separately.
Deals you can bring us
- New web-system development, or rebuilding and modernizing existing systems
- AWS/Azure/GCP builds, DB migration and performance work
- CI/CD adoption, server operations and monitoring
- Fixing systems that fail repeatedly, cutting cloud cost
- In-house AI / local-LLM adoption, and deals where dev is fine but there is no infra owner
Model case: web-system rebuild and AWS environment build
* This is a model case, not measured figures
How partner revenue is structured
- You can choose a structure where the customer contracts directly with the SES partner
- You can also choose a structure where the customer contracts directly with GIIP and the partner earns a referral/management fee
- Beyond a one-off referral fee, a management fee during the contract period can be set
- At the quote stage you can confirm the customer quote, GIIP's cost and the partner's profit
- The customer relationship and contact are, in principle, kept by the SES partner
- Specific fee rates and contract terms are decided after a per-deal discussion
We set fees for deal referral, sales support and account management according to the partner's role. Before proposing a deal, we make the customer quote, GIIP's cost and the partner's profit visible.
How this differs from offshore development
Overseas development companies in Vietnam, China, Thailand, Bangladesh and elsewhere are a valid option for securing development resources. Many have strong engineering and management, and quality cannot be judged by country alone.
In offshore development, however, information passes in stages between the sales rep, the bridge SE, the project manager and the development team — so differences in requirement interpretation, knowledge breaks from staff changes, and post-development operational responsibility can become issues.
GIIP FDE Box is not simply a way to supply low-cost developers. It continuously manages requirements, design, implementation, testing, cloud environment build, databases, deployment, monitoring and incident analysis within a single work history and approval flow.
What FDE Box prioritizes
- Continuously recording requirements, design decisions and work results
- Making production changes and critical operations subject to human approval
- Keeping not just source code but also environment configuration and operating procedures as deliverables
- Reducing the divide between development and infrastructure/operations
- Ensuring past decisions and work history remain traceable even when staff change
- Confirming per deal where customer data is stored, whether it is sent externally, and which AI models are used
- Defining the support scope through post-delivery monitoring, performance improvement and incident response
So FDE Box suits deals that value requirement accuracy, security, work visibility and post-delivery operations more than simply securing the cheapest developers. Beyond competing with offshore development, you can also manage and support an existing overseas team with FDE Box — the overseas team handles implementation while FDE Box complements it with requirements, review, environment build, deployment, monitoring and quality checks.
Security controls you can explain to the customer
Implementation status is confirmed per deal. We do not state unimplemented items in definitive terms.
Frequently asked questions
Which deals is it not suited to?
Deals requiring on-site presence only, deals requiring a named person's résumé, deals premised on the customer directing an individual directly, and deals needing a legally qualified named responsible party or physical on-site work may not apply as-is. We say so up front — we find it builds trust rather than erodes it.
What is the flow from sales to delivery?
(1) Share deal info → (2) review technical fit → (3) define scope and role split → (4) draft a joint proposal and quote → (5) the SES firm proposes to the customer → (6) after signing, the SES firm is the customer contact while GIIP executes development, infrastructure and operations → (7) regular reporting and handover of deliverables.
How does the SES firm profit?
(Model case) On a ¥3M/month development-and-operations deal, with the SES partner handling customer contact and requirements and GIIP handling development, build and operations, the partner reward is a sales/management margin per contract terms. Before the first meeting we share the assumed revenue, cost and partner profit. * This is a model case, not measured figures.
Why can GIIP support SES deals?
GIIP is not a mere generative-AI tool. It embeds engineering knowledge from 30-plus years of large-scale web services, databases, cloud migration, performance work and incident response into an AI multi-agent team's execution steps and approval flow. Humans approve anything hard to reverse.
How is the customer's information protected?
You can consult from a deal sheet with the customer name hidden. Data location, no use for external training, per-customer separation, access control and audit logs are defined under enterprise governance, and the scope of handling is agreed per deal.
Five options when an SES firm has deals but not enough engineers
Free deal-sheet diagnosis Escaping deep subcontractingEscaping multi-tier subcontracting to move up the flow
Free deal-sheet diagnosis From staffing to managed serviceShifting from man-month staffing to managed service (stock model)
Free deal-sheet diagnosisFree deal-sheet diagnosis, customer name hidden
No customer name or contact is needed. We review the deal outline and reply with feasibility, the recommended contract form, the role split between GIIP and your company, and an approximate structure. Before an NDA, you can consult with anonymous information only.