When is it useful to commission part of a project?
Do you have a client project and need a supplier for a defined part of the work? We can help when:
- You need additional expertise for the project. You want us to handle an integration or application extension while you coordinate the whole project.
- Your client needs a feature their system lacks. You need a supplier to design and build it.
- You need more information before preparing a proposal. Integration capabilities, data quality or difficult cases need checking to assess the scope and cost.
We tailor the engagement to your project and the division of responsibilities between suppliers.
ERP integration, automation and .NET application development
We design and implement connections between systems and features needed in your client’s process. The scope can include:
- Integration and data exchange. Reading information, transferring documents and statuses, validating data and handling errors. More about business system integration.
- Document automation. Preparing data from messages and attachments, matching it to system records and creating a draft for approval. For example: email orders to ERP.
- Software development. Designing and building .NET features, optimising MSSQL queries, preparing reports and exchanging data between applications. See custom software development.
- AI in an existing application. Document extraction, request classification or draft replies in software your client already uses. See AI integration with an application.
Our work draws on more than 20 years of IT experience: requirements analysis, system design and programming, and implementation. This also includes IT outsourcing. More about DO IT GLOBAL.
Example subcontracting scope: ERP and CRM
You are managing a CRM implementation, and your client needs ERP order statuses in it. You agree the workflow with the client and are responsible for the CRM implementation. You commission us to build the connection: mapping the required data, setting up exchange, handling errors and testing.
Before work starts, we agree who provides environments and documentation and who approves the result. You receive the agreed code and instructions to hand over to the client. This is an example division of work, rather than a completed client project.
How does working under your brand work?
In a white-label arrangement, the solution is presented to the client under your company’s brand. We can communicate solely with you or join agreed technical discussions with the client.
The engagement has three steps:
- Understand the task and system. We check requirements, documentation and data, drawing on your knowledge of the client.
- Build and test the solution. We design and program the required components, then check them against the acceptance criteria.
- Hand over the solution. We provide the documentation and instructions needed for ongoing operation.
You can also commission a feasibility assessment on its own to get the information needed for a project quote. We agree its price before starting.
Scope, acceptance and payment
The proposal defines the task, price, delivery date and acceptance criteria. We also identify who is responsible for system access, answering questions and approving requirements.
We charge a fixed price for a defined task or bill by time with an agreed limit. We quote for additional work before carrying it out, so you can account for its cost and timing in discussions with your client.
The contract defines confidentiality, data access, licence use and the handover of code and documentation. Further development and maintenance can be commissioned separately.
What should you send to get started?
A short task description, system names and versions, and the part of the project you want to commission are enough. Please do not send access credentials or confidential client documents at this initial stage.
During a free conversation, we will check how we can support your project and what we need to prepare a proposal.