Loading
How ConnectGo staffs your project
A small engineering company staffs a project with the people who build it. This page sets out which disciplines you get, which of them you deal with directly, and where the work hands over.
How the team is made up
Nine disciplines, drawn from the same list every scope document is staffed against. Which of them a project uses depends on the project; three of them you deal with directly whichever way it is staffed.
Founder / Director
You talk to them
Scopes the engagement with you and signs off what is in it. Stays reachable for the commercial questions rather than handing you to an account manager.
Software Engineer
You talk to them
Designs the system, writes the parts that hold it together, and is in the call where the technical trade-off gets made — not summarised afterwards.
Frontend Engineer
Builds the interface against the design: state, accessibility, performance budgets, and the behaviour on a mid-range phone rather than a desk machine.
Backend Engineer
Data model, APIs, integrations with whatever you already run, and the operational side — migrations, backups, logging you can read when something breaks.
Flutter Developer
One codebase for Android and iOS where that is the right call, native where it is not. Store submission and release builds included.
UI/UX Designer
Flows and screens before code, so a change is cheap while it is still a drawing. Delivers a component set the frontend builds from, not a picture of a page.
Project Manager
You talk to them
Owns the plan, the weekly update and the handover documents. The person who tells you a date has moved, before it moves.
QA Engineer
Tests each release against the written scope, on real devices and browsers, and keeps the regression pass that runs before anything reaches you.
Digital Growth Specialist
Search, analytics and measurement after launch — engaged when a system needs an audience, not attached to every project by default.
Publishing standard
A named profile is a claim a buyer can check, so it is held to the same standard as anything else on this site. The rebuilt version of this page carries the disciplines, the operating model and the handovers, all of which are true today. Names, photographs and biographies are added one at a time, each one on the terms below.
No leadership is named yet. The company has not confirmed a title in writing, and a founder is not something a website gets to decide. No Person structured data is emitted anywhere on this page while that is true — the gate is a data selector, not a comment, so it cannot be switched on by accident.
Roles, interview stages and the first-month plan are on the careers page.
What a profile needs before it goes live
01
Spelled the way the person wants it published, and the job they would state on a call with you. Not a title inflated to make a small team look larger — that is the specific failure this rebuild exists to correct.
02
A biography in the exact wording that goes live, read and agreed beforehand rather than shown afterwards, and an original photograph taken for this purpose. No stock library, no scraped avatar, no generated face.
03
Covering the name, the role, the biography, the photograph and any profile link. It is also what gates the machine-readable Person markup search engines read, which is far harder to take back than a web page.
How we work together
Six stages on one spine, and a named artefact at every handover. This is the operating model, not a description of it.
How this team works
Framed as practice rather than as company values, because the company has not ratified a set of values and inventing one would be exactly the kind of claim this site was rebuilt to remove. Each of these is observable in a scope document.
There is no account-management layer between you and the engineers writing the code. Whoever scopes your project is on the delivery, and answers your questions about the stack directly rather than relaying them.
Every engagement has one person accountable for it and it is stated in the scope document, along with who covers it while they are away. You never have to work out who to ask.
Design hands engineering components and states, engineering hands QA a reviewed pull request, QA hands launch a signed-off build. Each handover has a named artefact, which is why the six stages read as one team rather than five queues.
Repositories, environments and deployment notes are in your name from the first week, and the walkthrough goes to whoever will own the system afterwards. Nobody here is a single point of failure you inherit.
Where the team is
One team, in one place, working in Gujarat. Delivery runs on Indian Standard Time with an overlap that covers European mornings and the start of the North American day, and it is stated in the scope document rather than assumed.
The registered trading address is not published here yet. Two conflicting addresses are publicly visible for this company with different PIN codes, so it stays unrendered until the correct one is confirmed in writing rather than guessed at.
For engineers and designers
There is no open role listed today, and the careers page says so plainly rather than collecting applications against a vacancy that does not exist. The interview stages and the first-month plan are written out there, so you can decide whether it is worth watching.
For businesses
Ask who would work on it and what they have built before. You will get a straight answer, including when the answer is that we are not the right people for it.