Skip to content

Custom software development · Virginia

Custom software development company for Virginia.

We build custom platforms, SaaS products and mobile apps for companies in Virginia: government-adjacent technology and professional-services firms along the Dulles corridor in Arlington, Tysons, Reston and Herndon, operators of the data centers concentrated in Loudoun County, health systems and physician groups across Northern Virginia, and the associations and membership organisations headquartered around Alexandria. We work remotely from Ahmedabad, India, on Virginia's Eastern-time morning. There is no QalbIT office in the state, no cleared staff, and this page sets out exactly what both of those change.

Most vendor pages aimed at Virginia buyers say "serving the DMV" and stop. This one names what we actually build here, what we will not touch, and the row in the comparison table where a firm that can get a badge into the building is the only right answer.

  • 2018

    Building software since

  • 120+

    Projects delivered

  • 4 hours

    Live overlap, every working day

  • 5.0

    Clutch rating, 8 reviews

Get your free estimate

Three quick questions: scope, approach and a price range back within 48 hours. No sales call required first.

What do you need built?
When do you want to start?
Where should we send the estimate?

Answer all three questions above, then send.

NDA-friendly · IP yours from day one

Definition


What a remote software partner actually does for a Virginia organisation

QalbIT builds custom software for Virginia organisations as a remote engineering partner rather than a local firm. Two things shape most projects in this state: a working day that has to open on Eastern time, and a buyer population unusually well practised at vendor security review, because Northern Virginia sells software and services to federal agencies and to the contractors who serve them. We hold four live hours on Eastern time every working day from Ahmedabad, India, and we say plainly, before any proposal, which of your requirements a remote, non-cleared team simply cannot meet.

The difference that matters here is not how well the code is written. It is who can sign the contract and who can walk through the door.

A firm registered in Arlington or Tysons can put a badge-carrying engineer in your building, hold a facility clearance if the contract needs one, and sit inside whatever flow-down clause your own prime contract carries. A remote partner cannot do any of that. What it can do is take a defined, unclassified build, own the architecture and the release end to end, and do it for a fraction of the cost structure a cleared local team carries, because that overhead simply is not there to charge for.

Neither option is universally right. The work in front of you decides it, and we would rather say so on the first call than let a security questionnaire discover it in month three.

We are the remote, non-cleared option. This page is about exactly where that is useful and where it is not.

At a glance

  • Core focus

    Internal platforms, portals, SaaS products, mobile apps and the integrations between them

  • Engagements

    First builds · modernising a system the business has outgrown · modules over software you keep · standing engineering pods

  • Delivery

    Remote from Ahmedabad, live 08:00 to 12:00 ET Monday to Friday, a written handover before our day closes

  • Virginia position

    No office, no staff, no United States entity, no cleared personnel. Your paper, Virginia law

  • Ownership

    Your name on the repositories, the cloud accounts and the IP, assigned as each piece is written

Definition


Northern Virginia agency vs staffing firm vs remote engineering partner

Three things buyers here compare on an hourly rate when the rate is rarely the column that decides it.

  • Northern Virginia or DC-area agency

    Registered locally, able to hold a facility clearance, able to put engineers on site or inside a SCIF. You are buying eligibility as much as capability. The right choice whenever a contract requires US-person staff, a clearance, or physical presence.

  • Staffing or contract firm

    Engineers billed hourly into a process you already run, sometimes cleared, sometimes not. Architecture, code review, testing and release stay with your own technical lead. The right choice when you already have that lead and need more hands, cleared or otherwise.

  • Remote engineering partner

    A small senior team that owns a defined, unclassified build end to end, works your morning from outside the country, and hands over the repository at the end. No clearance, no US entity, so the contract, the tax paperwork and the security questionnaire are handled properly at the start. Best for internal tools, portals and products that do not touch CUI or classified systems.

We are the third. Where a contract needs the first two, we say so before an estimate is written, not after a deposit.

Fit


When a remote partner is the right call for a Virginia team, and when it is not

Most vendor pages argue one side of this. Here is the version with both sides on it, written for a state where the wrong answer has real consequences.

  • Hire a remote partner when

    • The system is unclassified, holds no Controlled Unclassified Information, and someone on your side can describe what it has to do without a clearance review.
    • The work is a defined build or module, an internal tool, a portal or a product, rather than a task order that requires US-person or cleared labour by contract.
    • Four hours of live contact each morning is enough, and the rest of your day can run on a written handover.
    • Owning the code matters to you: repositories, pipeline and documentation sitting in your accounts from sprint one, with nothing withheld to tie you to us.
    • Regulated but non-classified data is in scope, such as protected health information or personal data under Virginia law, and your compliance lead is willing to set the rules and review the evidence we produce against them.
  • Hire locally instead when

    • Your prime contract, task order or a flow-down clause requires US-person staff, an active clearance, or work performed inside a specific facility.
    • The system will hold Controlled Unclassified Information, classified information, ITAR-controlled technical data, or anything that would need to move through a cleared environment.
    • People have to be physically present: a data-center commissioning, a badge-access rollout, a hospital go-live, hardware on a rack.
    • Your security policy forbids any access to production data from outside the country and the work cannot be done against masked or synthetic data.
    • The engagement is really staff augmentation under your own architect, in which case a contract staffing firm will serve you better and cost you less management.

What that looks like in practice here

Virginia buyers, especially in Arlington, Tysons, Reston and Herndon, are unusually well practised at vendor security review, because so much of the region sells directly or indirectly to federal agencies and the habit of a formal questionnaire has spread well beyond companies that hold contracts themselves. The questionnaire arrives early, it names frameworks by number, and a vague answer gets noticed immediately. Where the honest answer is "we are not eligible for that," we say so on the call rather than let it surface after a proposal has been read. Outside Northern Virginia the buyer changes. In Richmond and along the I-95 and I-64 corridors it is more often a manufacturer, a distributor or a regional services firm with no federal work at all, and around Hampton Roads a carrier or broker tied to the port. Many of them search for custom IT solutions for businesses in Virginia and mean something narrower than the phrase: one system to replace the spreadsheet, the inbox and the overnight export that the operation actually runs on. That is the work we do, and the clearance questions above simply do not arise. We turn down Virginia projects that need a cleared or on-site team. A remote build attempted where a cleared local firm was the only lawful answer costs far more than the fee, and it is the kind of mistake a security review exists to catch.

Next step


Not sure which list your project sits in?

Tell us what the system has to do, what kind of data it will touch, and whether your contract carries a clearance or work-location requirement. We will tell you plainly which list you belong in, including when the answer is a firm in Arlington.

Comparison


Remote partner vs a Northern Virginia agency vs a staffing firm

Every row below is a real difference, including the rows we lose outright. Hourly rates are deliberately absent: we have no sourced figure for what firms in this market charge, and inventing one would be worse than leaving the column empty. We will run this against your actual contract terms and your data profile rather than against the generic case.

A remote engineering partner compared with a Northern Virginia agency and a staffing firm, row by row
Northern Virginia or DC-area agencyStaffing or contract firmQalbIT (remote partner)
Office you can walk intoYesSometimesNo
Live hours on Eastern timeFull working dayFull working day, usuallyMornings, 08:00 to 12:00 ET, then a written handover
Eligible for cleared or CUI-handling workOftenSometimesNo
Who owns the architectureThe agencyYou doWe do, reviewed with your technical lead
Who owns testing and releaseThe agencyYou doWe do, with your sign-off as the gate
Contract and governing lawDomesticDomesticYour paper, Virginia law, invoiced in US dollars
Source code and IPVaries by contractYoursYours, assigned as the work is created
Security questionnaires and insuranceRoutineRoutineCompleted by us, certificates of insurance on request
People on your accountMove with the agency workloadRotate with the contractSmall, senior, named in the proposal and unchanged
  • 01

    The "No" row is the one that matters most here.

    If your project needs a cleared engineer or a facility, that row settles the decision by itself, and no amount of engineering quality on our side changes it. We would rather that be obvious on this page than discovered at a security review.

  • 02

    Presence and delivery are different questions everywhere else.

    For unclassified work, your platform can run on infrastructure in a US region, under your own cloud account, while the engineers building it sit elsewhere. That distinction settles most of a vendor-risk conversation once a project is confirmed to be outside the cleared category.

  • 03

    A staffing firm and an engineering partner are not substitutes.

    A staffing firm sells capacity for a process your own lead already directs, which suits a Reston prime with a strong technical lead. Without that lead owning architecture, code review and release quality, more engineers mean more code sooner, not a working system sooner.

  • 04

    Ask the eligibility question before the estimate question.

    A prime contract, a task order or a customer flow-down clause naming a clearance or a work-location requirement is binary. Ask us on the first call and the answer comes back the same day, before anyone spends time on a proposal that cannot be accepted.

What we build


Custom software we build for Virginia organisations

Unclassified systems that hold up under a vendor security review: internal tools, portals and platforms with the access control and audit trail a Virginia buyer's questionnaire will ask about by name.

  • Internal tools

    Back-office and contract-operations platforms

    Intake, task tracking, deliverable status, timekeeping and reporting for professional-services and technology firms serving federal clients, built around your own process rather than a template. Unclassified, and designed that way from the first requirement.

  • Portals

    Customer, member and vendor portals

    A portal on top of the system you already own, with role-scoped access, an audit trail and document handling that survives a review. A natural fit for the associations and membership organisations concentrated around Arlington and Alexandria.

  • SaaS

    SaaS products and MVPs

    Multi-tenant products with billing, roles, usage limits and an audit trail, for a founding team that needs paying users before the next raise, or a company productising something it already runs internally.

  • Mobile

    Mobile apps for people away from a desk

    One Flutter codebase across iOS and Android for field technicians, facility staff and member-facing teams, built offline-first because a basement server room or a rural site visit is not your user's problem to solve.

  • Integrations

    APIs and integration engineering

    Wiring a CRM, a case-management system, a payment processor or a health record together, with queues, retries and a reconciliation view so a failed message is visible rather than silent.

  • Cloud

    Cloud environments and delivery pipelines

    AWS accounts in your name, often in the same US-East region physically anchored in Northern Virginia's data centers, with infrastructure as code, staged releases and the access logs a vendor security review will ask you to produce.

Cost


How much does custom software development cost in Virginia?

Custom software for a Virginia organisation is priced on the scope of the first release, the number of systems it integrates with and the compliance evidence it has to produce, not on headcount. At QalbIT, fixed-scope projects start from $5,000, a scoped MVP included, and dedicated engineers from $3,200 per engineer per month. A written scope with the exclusions named comes back within 48 hours of the first call, and a first release usually lands 6-14 weeks after that scope is signed.

Those floors are QalbIT’s own, and nothing else on this page puts a price on software. Ranges published for this question tend to span an order of magnitude with no source behind them, and we will not add another.

We also do not publish what a Northern Virginia agency charges, because we have no figure we could attribute to anyone, and rates near a federal buyer market are not the same as rates elsewhere. Ask three firms in the region for a quote on the same written scope and you will have better information than any page on this subject can give you.

So the price comes after the scope: one discovery call, a written scope naming what is excluded, and a fixed figure for phase one before you commit past discovery. The drivers below are what move that figure, and they work as a checklist against any quote you are sent, ours included.

Try the software development cost calculator

What moves the number

  • Scope of the first release

    Nothing moves the price more. A contracts team is better served by one finished workflow, task-order status from award to invoice for instance, than by four half-built ones, and a finished first release is what a second phase gets funded from.

  • Integration count and quality

    Each connected system adds scope, and not equally. A documented REST API with OAuth is straightforward. A legacy case-management or contract system with a nightly file export needs a middleware layer and a reconciliation view of its own.

  • Compliance evidence

    Access reviews, audit trails and the artefacts a vendor security questionnaire asks for are engineering work with their own timeline. Designed in at the start they are modest. Retrofitted after a finding they are a project.

  • Roles and approval rules

    Two user types is a data model. Nine user types with delegated approval, segregation of duties and a maker-checker rule is a system in its own right, and it is where operations software quietly grows.

  • Platform count

    A web app alone, web plus one mobile platform, or web plus iOS and Android working offline for technicians in a server hall or on a rural site visit. Each step adds build, test and release work, and offline sync adds conflict rules that somebody has to design.

  • Data migration depth

    Moving master records and open items is routine. Moving years of transactional history, reconciled against the old system and signed off by finance, is a workstream that deserves its own estimate.

How we work with Virginia teams


A delivery process built around the Eastern-time morning

The offset is real, so we plan around it rather than pretending it away. Your morning is our evening: 08:00 to 12:00 ET is our late afternoon and evening in Ahmedabad, and every call, demo and decision lives inside that window.

  1. Discovery and written scope

    One call to walk through how work moves today, who touches it, where it breaks and whether any part of it needs a cleared or on-site team, then a written scope with the exclusions named. Nobody here estimates from a conversation alone, and the document is yours whether or not you hire us.

    Your process mapped on paper, an estimate range for phase one, and the person who would lead the build.

    48 hours

  2. Prototype and architecture

    A clickable prototype in week one, so your stakeholders react to real screens instead of a requirements document. Alongside it: the data model, access control, hosting region and the rollback path, agreed in writing before anyone touches a repository.

    Approved screens, an architecture your technical lead can read, and a data-handling position your compliance team has seen.

    1-2 weeks

  3. Build in fortnightly slices

    Working software demoed every two weeks, live in your morning, against your real records rather than dummy data. Each slice is checked against the scope in front of you, so progress is watched rather than reported.

    Modules checked against the cases your contracts or member team handles every week, and a backlog whose order you set sprint by sprint.

    6-14 weeks, scope-dependent

  4. Harden, then release

    Permissions, load behaviour, backups, monitoring and a tested rollback are signed off before anything reaches your users. Where a vendor questionnaire or an access review is required, the evidence is produced here rather than promised.

    A release your security reviewer can accept, with the evidence attached rather than described.

    2-3 weeks

  5. Improve and extend

    Monitoring, iteration and the next slice of roadmap with real usage data behind it, on a support window that matches your Eastern-time day.

    A system that stays worth running, and a handover to your own staff whenever you decide to take it in-house.

    Monthly, 30 days notice

Virginia runs Eastern time and our team runs India Standard Time: roughly a nine-and-a-half-hour offset while Virginia keeps daylight saving, ten and a half once it does not, with four hours of every working day live together. Stand-ups, demos and decision calls sit in your morning, and a written handover goes out before our day closes, so your afternoon is never spent waiting on an answer from us.

Book a scoping call

Where we fit best


Virginia projects we take on

These are the engagements that work well from a distance, without a clearance and without a badge. The ones that do not are listed higher up the page, and we mean that list.

  • Internal tools

    Replacing the spreadsheet that runs contract operations

    Deliverable tracking, timekeeping, task-order status and reporting held together by workbooks and one person who knows the exceptions, rebuilt as a system with roles, approvals and a history of who did what. Unclassified throughout. For operations and contracts teams at professional-services and technology firms.

  • Modernisation

    Rebuilding software you have outgrown

    An old desktop tool or an early web application rebuilt as a maintainable platform, without losing a decade of data or retraining everybody in a weekend. For organisations stuck on a system nobody supports any more.

  • Member portals

    Building a self-service portal for members or customers

    Account management, document access, dues or subscription handling and a support history a member can see for themselves, so the phone stops ringing for questions a portal can answer. For associations, membership bodies and service organisations.

  • Extension

    Extending what you already own

    Custom modules, portals, dashboards and integrations layered on top of a CRM, a case-management system or a health record, so you keep the system of record and lose the retyping around it. For organisations extending rather than replacing a core system.

Industries


Sectors we build for in Virginia

Operational software is shaped by its sector. These are the parts of Virginia's economy where our process knowledge transfers, and where the compliance questions are ones we have thought through in advance.

  1. Federal contracting and government-adjacent technology

    Arlington, Tysons, Reston and Herndon along the Dulles corridor carry one of the country's densest concentrations of federal contractors and the technology and consulting firms that serve them. We build the unclassified side of that world: proposal and contract-operations tooling, timekeeping, internal dashboards and customer-facing portals. We do not hold a facility clearance and we do not touch Controlled Unclassified Information, and we say that up front rather than let a security review find it.

  2. Data centers and cloud infrastructure

    Loudoun County calls itself Data Center Alley and describes the concentration of data centers around Ashburn as the highest anywhere in the world. Amazon Web Services opened its first region, US East (N. Virginia), there in 2006. Operators, managed-service providers and the vendors around them need internal tooling for capacity planning, ticketing, vendor and access management, not the data-center build itself, which is a different trade entirely.

  3. Healthcare providers across Northern Virginia

    Scheduling, intake, referral and care-coordination tooling around an existing record system, for hospital systems, physician groups and specialty practices. Where protected health information is in scope we build to the HIPAA Security Rule technical safeguards and work under the rules your privacy officer sets, rather than making promises about them on a web page.

  4. Associations and membership organisations

    Arlington and Alexandria host a dense concentration of national trade associations, professional societies and membership nonprofits. The recurring need is a member portal: dues, renewals, event registration, resource libraries and a support history, layered over the association-management platform most of these organisations already run.

  5. Manufacturing and distribution around Richmond

    Order management, inventory across warehouses, job costing and the customer and supplier portals that manufacturers and distributors in Richmond, Chesterfield and Henrico outgrow a spreadsheet for. Many already run an ERP they would rather keep, so the usual first build is a custom ERP module or a portal over it, with the integration that stops the same order being typed into three systems.

  6. Logistics around the Port of Virginia

    Hampton Roads is home to the Port of Virginia, one of the busiest container ports on the US East Coast. Carriers, brokers and distributors moving freight through the region need appointment scheduling, yard visibility and reconciliation across systems that each think they own the shipment.

  7. Higher education and research computing

    Data-heavy research tools, grant and lab-management systems, and the first commercial platform a university research group builds when a tool made for its own lab turns out to be worth sharing more widely.

If your sector is not on that list, the question we will ask first is the same one: what does a day of this work look like, and does any part of it need a clearance we do not have?

Next step


The off-the-shelf product does not fit how your operation runs.

That is usually what starts a custom build. Describe the process and we will tell you honestly whether it justifies a project, or whether configuring what you already run would do.

Virginia compliance


Building software for Virginia: privacy, federal cybersecurity rules and breach duties

These are the obligations that decide how a system is built in this state, and the questions a supplier outside the country has to answer before you sign anything. We are engineers and not your counsel: what follows is what we build, not legal advice about what applies to you.

  1. The Virginia Consumer Data Protection Act

    In force since 2023. Signed in March 2021 and in force since 1 January 2023, the Virginia Consumer Data Protection Act was the second comprehensive state privacy law in the country. It applies to persons that conduct business in Virginia and, during a calendar year, control or process the personal data of at least 100,000 Virginia consumers, or of at least 25,000 consumers where the business derives over 50 percent of gross revenue from selling personal data. It gives residents rights of access, correction, deletion, portability and the right to opt out of targeted advertising, the sale of personal data and certain profiling, and requires a data protection assessment for higher-risk processing. Enforcement sits exclusively with the Office of the Attorney General, which must give notice and a cure period before bringing an action. The engineering work is the same shape regardless of who enforces it: a data inventory, a consent state, an opt-out signal handler, request workflows with a clock on them, and deletion that reaches backups and exports rather than stopping at the primary database. Whether you are in scope is a question for your counsel. What we build is the machinery, and we build it whether or not the threshold is met, because retrofitting it later is always the more expensive path. Sources: Virginia Consumer Data Protection Act, Va. Code §§ 59.1-575 to 59.1-585 · Office of the Attorney General of Virginia.

  2. CMMC and DFARS cybersecurity requirements

    Defense contractors. A Northern Virginia firm working under a Department of Defense contract or subcontract that handles Controlled Unclassified Information is generally subject to the Defense Federal Acquisition Regulation Supplement clause requiring implementation of the NIST SP 800-171 security controls. Since 10 November 2025 it can also find a Cybersecurity Maturity Model Certification requirement in the solicitation itself: the DFARS clause 252.204-7021 took effect that day, on top of the CMMC programme rule in force since December 2024, and a contract's required level decides whether a self-assessment or a third-party assessment is needed. The rollout is phased, so which new awards carry the clause depends on the programme office for now. We do not build for that boundary. QalbIT has no facility clearance, no cleared personnel and no system authorised to hold Controlled Unclassified Information, so any part of a Virginia engagement that would put CUI into a system we build has to stay out of scope, or the engagement is not one we can take. Whether your contract requires CMMC, at what level, and from which award is a question for your own compliance and contracts team. We flag the boundary; we do not advise on where your obligation currently sits. Sources: Defense Federal Acquisition Regulation Supplement 252.204-7012 and 252.204-7021 · NIST Special Publication 800-171 · CMMC Program, 32 CFR Part 170 · US Department of Defense.

  3. FedRAMP for cloud services sold to federal agencies

    A cloud service intended for use by a federal agency generally needs a FedRAMP authorisation, built on the NIST SP 800-53 control catalogue. Today it is signed either by an agency’s authorizing official or, for a program authorisation, by the FedRAMP Director, after an independent assessment of the service. The Joint Authorization Board that older guides mention has been replaced by the FedRAMP Board, which sets the rules rather than approving individual packages. Where a Virginia client is building toward that outcome, we design to the relevant control families from the outset, roles, logging, encryption, configuration management, so the eventual assessment finds evidence rather than gaps. The authorisation decision itself belongs to the sponsoring agency and the assessor, never to us. We are not a 3PAO and we do not issue or promise an Authority to Operate. We build the system to the control set your sponsoring agency and assessor expect to see. Sources: FedRAMP Authorization Act and programme baselines · OMB Memorandum M-24-15 · NIST Special Publication 800-53 · General Services Administration.

    Federal cloud

  4. ITAR and export-controlled technical data

    Plenty of Dulles-corridor firms hold defense work whose drawings, specifications or source code are technical data under the International Traffic in Arms Regulations. Showing that data to an engineer in India is an export in its own right, and it needs State Department authorisation before it happens, wherever the server sits. Our team is in Ahmedabad, so any part of a project that carries ITAR technical data stays with a US firm that can staff it with US persons. The software around that boundary is a different matter: a proposal tracker, a timekeeping and contract-operations tool, a training and certification register, a customer portal that never stores controlled drawings. We build that side, and its access and upload rules are agreed with your export-control officer so controlled files stay out of it. Whether a file, a dataset or a code base is ITAR-controlled is your empowered official’s or export-control officer’s call, not ours. Tell us on the first call and the eligibility answer comes back the same day. Sources: International Traffic in Arms Regulations, 22 CFR Parts 120 to 130 (export defined at § 120.50) · US Department of State, Directorate of Defense Trade Controls.

    Defense articles

  5. HIPAA technical safeguards for protected health information

    Where a system touches protected health information we build to the HIPAA Security Rule technical safeguards: unique user identification, automatic logoff, role-scoped access, encryption in transit and at rest, integrity controls, and an audit trail that records who read a record and not only who changed it. We do not promise a business associate agreement on a web page. Whether one is required is decided by your privacy officer and your counsel. We build to the safeguards and hand them the engineering evidence they need to sign the position off. Sources: HIPAA Security Rule, 45 CFR Part 164 Subpart C · US Department of Health and Human Services, Office for Civil Rights.

    Health data

  6. Breach notification under Virginia law

    Virginia requires an individual or entity that owns or licenses computerised personal information to notify both the Office of the Attorney General and every affected Virginia resident of a breach of the security of the system, without unreasonable delay. Where notice goes to more than 1,000 people at one time, the Attorney General and the nationwide consumer reporting agencies must also be told when the notice went out, how and what it said. You cannot notify accurately unless the system can say which records were reached and by whom, so retained access logs, an audit trail that resists tampering, alerting on unusual access and a rehearsed procedure for reconstructing an incident are part of the build rather than a policy statement. Whether and when to notify, and what the notice says, is decided by your counsel under your incident response plan. Our job is to make sure the system can tell them, quickly and accurately, which Virginia records were reached. Sources: Code of Virginia § 18.2-186.6 · Office of the Attorney General of Virginia.

    Incident duty

  7. SOC 2 vendor questionnaires

    Most Virginia buyers of any size, and nearly all of the government-adjacent ones, send a vendor security questionnaire mapped to the Trust Services Criteria before a contract is signed. We complete it ourselves rather than returning a brochure, answering with what we operate: named access with least privilege, change management through pull request and review, environment separation, logging and retention, backup and restore testing, staged releases, incident handling and a documented offboarding step when an engineer rolls off. Where an answer is no, and for the clearance and CUI questions it usually is, it is written as no. A questionnaire padded with paragraphs around a hard no is how a supplier gets removed from a shortlist late, and we would rather be removed early. Some Virginia buyers require the supplier to hold its own attestation report. If yours does, say so on the first call: you get our current position in a sentence, and if it falls short of your bar you hear that before the questionnaire does. Sources: AICPA Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality and Privacy.

    Vendor risk

We build systems that produce this evidence natively rather than bolting a compliance module onto software that resists it. Where a Virginia buyer's questionnaire is driving your timeline, that document is where we start planning backwards from.

Working with us


Hiring a vendor outside the United States: the honest version

Your legal, finance and security teams will each have a short list of questions about a supplier outside the country, and a Virginia buyer's list is usually longer than most. Here is ours, with the answers.

  • The contract

    We sign on your paper. Virginia law governs, and jurisdiction, venue, liability and termination follow your counsel’s draft. We never ask a client to contract under foreign law, and no engagement begins without a signed agreement.

    Governing law

  • Tax paperwork and invoicing

    Because QalbIT is not a US entity, your accounts payable team gets a completed Form W-8BEN-E before we raise the first invoice. Invoices are in US dollars, each against a contract milestone or the monthly rate, and each carries your purchase order number.

    W-8BEN-E

  • Intellectual property

    Assignment happens as the work is produced, so code, designs, documentation and infrastructure definitions are yours before the final payment rather than because of it. Repositories, cloud accounts and domains sit in your name from the first commit, and each engineer on the account is bound by the same assignment and confidentiality terms.

    Assignment

  • Confidentiality

    Before anything sensitive is shared we sign an NDA, normally mutual, on your template or ours. Your organisation, your product and your project are never cited as a reference unless you agree to it in writing.

    NDA

  • Insurance and security questionnaires

    Certificates of insurance are provided on request. Security questionnaires are completed by the people who would do the work, not by a sales team, and the answers describe what we actually operate, including where the honest answer is no.

    Vendor risk

  • Background checks

    Where your policy requires background checks on named engineers, we arrange them and return the results through your process. We cannot arrange a security clearance, and we say so before it becomes a blocker at contract stage.

    On request

  • No local entity, no clearance, and what that rules out

    QalbIT has no United States entity, no Virginia office, no cleared personnel and nobody who can be in your building on Tuesday. Where a procurement rule, a grant condition, a clearance requirement or a client flow-down requires any of those, we are not eligible, and you will hear that on the first call rather than after a proposal.

    The limit

None of that is a reason to avoid a remote partner for the work that fits. It is a reason to handle the paperwork, and the eligibility question, properly at the start instead of assuming it away.

Tech stack


Technology we use for Virginia builds

Internal systems and member portals live for a decade, so we choose technology a new engineer can read in an afternoon and your future team, internal or not, can maintain without us.

  • Backend and business logic

    • Laravel (PHP 8) for modular business systems with strong audit trails.
    • Node.js and NestJS where integrations and event-driven flows dominate.
    • Queues, schedulers and retries for syncs, alerts and report generation.
  • Interface and usability

    • Next.js and React, server-rendered where search traffic matters.
    • Keyboard-first data entry for screens people live in all day.
    • Flutter for one mobile codebase across iOS and Android, offline-first.
  • Data and integrations

    • PostgreSQL and MySQL with constraints that protect financial and membership data.
    • Versioned records and append-only audit trails where evidence is required.
    • REST and GraphQL integrations with CRMs, case-management tools and record systems.
  • Security and delivery

    • AWS accounts in your name, often in the same US-East region anchored in Northern Virginia, defined in Terraform rather than by hand.
    • Least-privilege access, logged, with break-glass reviewed after use.
    • Staged releases through GitHub Actions, every one reversible.

Already running something on Salesforce, an association-management platform or a legacy .NET system? We extend what works rather than rewriting it for the sake of a stack preference, and we say so in writing before anyone touches a repository.

Outcomes


What the project should actually change

No forecasts here. Each row names a change a Virginia contracts office, member-services desk or operations team should see, and the measure that proves it happened.

What the project should actually change: what changes and how you would measure it
What changesHow you would measure it
One record of the truth across systemsValues that still need reconciling by hand between systems
Work moves without being retypedHand-offs that still require a person to copy a value
Approvals are enforced rather than rememberedShare of transactions with a complete approval trail
Access and audit requests are answered from the systemHours to produce an access, deletion or audit response
Incidents can be scoped preciselyTime to establish which records were reached, and by whom
Managers see position without asking anyoneTime from question to answer
  • A note on sourcing

    A note on sourcing

    We do not quote market figures on this page: not Virginia salary bands, not agency rates, not the failure-rate statistics that circulate without a traceable primary source. The only numbers here are our own, and each one names where it comes from. If a figure matters to your decision, ask for the source and we will send it or withdraw the claim.

Why QalbIT


Why Virginia organisations keep us on the project

  1. Building this kind of software since 2018

    Since 2018: 120+ engagements, 50+ clients, and a mix of web, mobile and platform builds. The public record: Clutch 5.0 across 8 reviews, Google 4.9 across 18, and 100% job success on Upwork. We can show you each figure, and we quote no others.

  2. We work your mornings, properly

    Four hours of live overlap every working day, 08:00 to 12:00 ET. Calls, demos and decisions happen in that window, and a written handover lands before our day closes so nothing waits for a status meeting.

  3. We say what we are, and what we are not

    No Virginia office, no Virginia staff, no United States entity, no cleared personnel, and no implied presence anywhere on this site. Where a project needs any of those, we say so before the call ends rather than at the security review.

  4. The named engineers are the ones who build it

    Every name in the proposal belongs to a person who commits to your repository. None of the build is subcontracted, nobody is moved to another account halfway through a sprint, and the founder answers your email without an account manager in between.

  5. We will tell you to hire locally, or a cleared firm

    When your project needs a facility clearance or a badge in the building, you hear it on the first call. It costs us a project and saves you a failed security review, and it is the reason a fair number of our engagements arrive as referrals.

The biggest difference has been their flexibility and solution-oriented approach. Rather than pointing out problems, they focus on solving them. I genuinely cannot recall hearing them say, ‘This cannot be done.’ No matter how many changes or updates we send their way, even after long working days, they consistently respond positively and find a way forward. What stands out most is that our relationship has evolved beyond a traditional client-supplier setup and feels more like a partnership. QalbIT takes genuine responsibility for the platform’s functionality, and when bugs are identified, they are addressed without hesitation.
Gabriell Summerland, CEO, Bluecircle

FAQs · Custom software development in Virginia


Questions Virginia teams ask before they start

Eastern-time cover, budgets, clearances, paperwork and who owns what, answered the way we would answer them on a call.

Talk to the team
No to both, and we lead with that rather than let it surface at security review. QalbIT has no facility clearance, no cleared personnel and no system authorised to hold CUI, so anything under a DFARS 800-171 or CMMC boundary is out of scope for us. Tell us on the first call whether your contract or flow-down clause requires cleared staff, and you will have an honest answer the same day, before anyone drafts a proposal.
A cloud service sold to a federal agency generally needs a FedRAMP authorisation against the NIST 800-53 controls, issued as an Authority to Operate by a sponsoring agency. That authorisation process sits with your organisation, not with us; what we can do is build the surrounding, unclassified system correctly from the start so it does not have to be rearchitected when that review begins.
Because so much of Northern Virginia sells to federal agencies or their contractors that the habit of a formal vendor questionnaire has spread well past companies that hold contracts themselves. Asking early, about clearance, CUI and work-location clauses, means we tell you plainly when we are not eligible instead of a proposal getting quietly rejected weeks later.
You do, from the first commit, assigned as the work is created rather than at final payment. For unclassified projects the infrastructure is typically AWS, in your own account, often physically anchored in the same Northern Virginia region your data already sits in, defined in Terraform rather than configured by hand.
The offset runs nine and a half hours for most of the year and ten and a half once Virginia drops daylight saving, so our evening is your morning. We hold four hours live on your Eastern-time morning for stand-ups and decisions, and a written handover closes our day so your afternoon is never spent waiting on a reply.
Virginia law requires whoever owns or licenses the computerised personal information to notify the Attorney General's office and affected Virginia residents of a breach without unreasonable delay. If notices go to more than 1,000 people at one time, the nationwide consumer reporting agencies must be told as well. We build logging, access control and an incident process so that notification, if it is ever needed, is based on evidence rather than guesswork.
Yes, gladly, and it is unrelated to the clearance question above: an NDA covers ordinary confidentiality, not classified access. Send yours or use ours, either way it is in place before any detail about the system changes hands.
Yes, when the software sits outside the controlled boundary. A proposal tracker, a timekeeping or contract-operations tool, or a customer portal for a firm in Tysons or Reston is ordinary commercial work if it never holds Controlled Unclassified Information, classified material or ITAR technical data, and if your contract carries no US-only performance or cleared-staff clause. Your contracts and export-control team draws that line, not us. Once it is drawn, the system’s upload and access rules are written to keep controlled files out, and anything that would cross it stays with a US firm.
QalbIT builds association software for trade associations, professional societies and membership nonprofits around Alexandria and Arlington, remotely on Eastern mornings. Usually the job is to extend the association-management platform the organisation already runs: a member portal for dues and renewals, event registration, committee workspaces and a resource library, all reading from one member record. Replacing the platform outright is sometimes right, typically when its API cannot support what members now expect, and the written scope says which case you are in before a price is attached. Years of member and payment history are migrated and reconciled as a workstream of their own.
We do, as a remote team on your Eastern-time morning, for consulting and professional-services firms along the Dulles corridor. A consulting firm’s CRM is less a sales funnel than a capture system: opportunities tracked from forecast to award, teaming partners, bid and no-bid decisions, proposal deadlines and the past-performance record each bid draws on. Where an opportunity file would ever hold Controlled Unclassified Information, that material stays in your own controlled environment and the CRM keeps only a reference to it. Fixed-scope work starts from $5,000, and a written range for your build follows the first call within 48 hours.

Next step


Let us scope the first release.

Tell us how work moves through your organisation today, where it stalls, and which date cannot move. We will map it, name the system that earns its place first, and put an honest price range against a phased plan. If your project needs a cleared or local Virginia firm, that is what the reply will say. Expect a written scope, exclusions named, within 48 hours, and keep it whatever you decide.