Client background
Premium Oilfield Technologies is a Houston, Texas-based manufacturer of equipment for the oil and gas industry. With 201 to 500 employees and a global client base in energy production, the company designs and manufactures highly engineered components that are critical to drilling and extraction operations. The engineering culture at the company had historically been focused entirely on hardware: mechanical engineers, materials scientists, and manufacturing specialists. Software had been treated as a secondary concern, purchased from vendors or handled by IT generalists rather than developed as a core competency.
By 2023, this approach was no longer sustainable. The company's clients and the broader energy sector were demanding digital capabilities that the company's existing software infrastructure couldn't support: real-time equipment telemetry for predictive maintenance, digital twin integration for equipment configuration and performance modelling, and customer-facing portals for order tracking, documentation, and technical support. Maniram M., the Global Sourcing Head, was tasked with building the company's first internal software development capability — a pilot team that could prove the value of software investment and establish the hiring, management, and delivery patterns that would guide a broader digital transformation.
The oil and gas sector's digital transformation had been accelerating across the industry, driven by both cost pressure and client expectations. Enterprise procurement teams at major energy operators were increasingly evaluating suppliers not just on the quality of their physical components but on the quality of their digital integration — the ability to provide real-time performance data, support predictive maintenance programmes, and connect to supply chain management systems via API. For Premium Oilfield Technologies, building a credible software capability was not merely an internal efficiency initiative; it was a competitive requirement for retaining and expanding relationships with their most sophisticated clients.
The challenge
Building a software development team from scratch inside a hardware company is harder than it sounds. The challenges operate at multiple levels simultaneously. At the talent level, Houston is not a software engineering hub — the local engineering talent market is heavily skewed toward energy sector engineering (mechanical, petroleum, chemical), and the software engineers who are available locally expect Silicon Valley-competitive compensation that a manufacturing company's HR function is typically not designed to provide.
At the organisational level, a pilot software team inside a hardware company needs to demonstrate value quickly to earn the internal credibility required for continued investment. A team that takes six months to ship its first feature will not survive the inevitable internal scepticism from departments accustomed to purchasing software from established vendors. The first few deliverables need to be concrete, visible, and aligned with business priorities that the company's leadership cares about.
At the management level, a newly formed software team inside a hardware company almost certainly lacks experienced software engineering management. Without strong technical leadership, teams without engineering management experience tend to accumulate technical debt rapidly, struggle with prioritisation, and miss deadlines in ways that damage the credibility of the entire digital initiative.
Maniram M.'s approach was to use a staff augmentation partner not just to provide bodies, but to provide a team that could establish patterns and practices from the start — a team with both the technical skills to deliver and the engineering culture to set the right precedents for how software development should work inside Premium Oilfield.
How we engaged
Squash Apps was selected after an online search and competitive vetting process that included multiple providers. The selection criteria were strong cultural fit, demonstrated capability in the relevant technology areas, and a track record of building and managing teams rather than simply placing individual contractors.
The engagement structure was deliberately designed as a pilot: a team of 6 to 10 engineers assembled over the first three months, operating on a six-month initial commitment with a clear evaluation framework at the end of the pilot period. This structure gave Premium Oilfield a defined evaluation point while giving the Squash Apps team enough time to deliver meaningful results rather than being assessed on sprint-one output.
The team was built around the specific technology priorities identified in the initial scoping: full-stack web development capability (for the customer portal workstream), API development experience (for the equipment telemetry integration), and cloud infrastructure skills (for the AWS deployment architecture). Each engineer brought to the engagement had been specifically vetted against these requirements through the Squash Apps four-stage vetting process — résumé review, technical assessment, live code review, and CTO sign-off.
Srijith was involved in the initial team assembly and client kick-off meetings, establishing the delivery standards and communication norms that the team would operate by. Maniram M. noted in his Clutch review that the working culture and team talent were standout attributes of the engagement from the first interactions.
What we built
The pilot team's deliverables were organised around three priority workstreams identified during the initial scoping: customer portal, equipment telemetry API, and internal tooling.
The customer portal was the highest-visibility deliverable: a web application giving Premium Oilfield's clients access to their order history, equipment documentation, technical specifications, and a structured channel for warranty claims and technical support requests. This replaced an email-and-PDF workflow that had been a consistent source of friction in customer relationships. The portal was built as a React frontend with a Node.js API, deployed on AWS with role-based access controls distinguishing customer users from Premium Oilfield's internal service and sales teams.
The equipment telemetry API was the more technically complex workstream: building the data ingestion and storage infrastructure that would receive sensor data from instrumented equipment in the field, store it with the appropriate time-series architecture, and provide query interfaces for both real-time monitoring and historical trend analysis. This infrastructure was the foundation for the predictive maintenance capabilities the company intended to build in subsequent phases.
Internal tooling covered a set of smaller applications that reduced manual work in the manufacturing and field service operations: a spare parts request and approval workflow (replacing a paper-based system), a digital checklist system for field service engineers (replacing physical inspection forms), and a quality control data entry interface (connecting field measurement data to the existing quality management system).
Technical approach
The technology stack reflected the team's capability mix and the client's cloud strategy. The customer portal and internal tools were built on a React/Node.js/PostgreSQL stack, deployed on AWS Elastic Beanstalk with RDS for managed database hosting. The telemetry infrastructure used AWS IoT Core for device data ingestion, Amazon Timestream for time-series storage, and AWS Lambda for the real-time data processing functions.
Infrastructure-as-code was implemented from the start using Terraform — a deliberate choice to ensure that the infrastructure was reproducible, version-controlled, and not dependent on manual configuration that would create operational risk as the team grew. This approach also meant that the company would be able to scale the infrastructure independently as usage grew, without needing to reverse-engineer what had been manually configured.
API design followed RESTful conventions with OpenAPI documentation generated automatically from the code, giving the internal team and eventual future developers clear, accurate documentation of every endpoint. This was a specific early investment in the maintainability of the codebase that would reduce onboarding time for engineers added to the team in later phases.
Results
At the conclusion of the initial pilot period, Premium Oilfield had a functioning software development team delivering against a product roadmap — which was precisely the outcome the engagement had been designed to achieve. The customer portal went live with the company's three largest clients during the pilot period, receiving positive feedback from client contacts who had been frustrated by the previous email-based workflow.
The equipment telemetry infrastructure was deployed to a pilot cohort of instrumented equipment, demonstrating the data collection capability that would underpin the predictive maintenance initiative in subsequent phases. The internal tooling workstreams had reduced manual data entry in manufacturing and field service operations, freeing up technicians and field engineers to focus on higher-value work rather than form-filling and manual reporting.
The pilot also achieved its less tangible but equally important goal: establishing proof-of-concept for software development as a core internal competency at Premium Oilfield. The engineering team delivered against commitments in ways that shifted the internal perception of custom software from a risky unknown to a dependable investment. This cultural shift — from scepticism about software to confidence in it — was a prerequisite for the broader digital transformation programme the company was planning.
Maniram M.'s assessment: "I'm impressed with their working culture and highly talented crew." He noted specifically that the team delivered more than expected — a result that reflects both the engineering quality of the individuals placed and the management culture that Squash Apps brought to the engagement. For organisations embarking on a digital transformation in capital-intensive industries, the Premium Oilfield engagement illustrates how a well-structured staff augmentation model can provide both the technical execution and the cultural infrastructure needed to build a lasting internal capability. The engagement has continued and expanded beyond the initial pilot scope.