Build vs Buy: International Student SEVIS Compliance Software
Buy. This is one of the few categories where we tell almost every institution to choose a product: Sunapsis or Terra Dotta ISSS encode years of regulatory detail, and a home grown gap risks your certification to enrol F and J students.
On this page
Buy. This is one of the few categories where we tell almost every institution to choose a product: Sunapsis or Terra Dotta ISSS encode years of regulatory detail, and a home grown gap risks your certification to enrol F and J students. Build only when several SEVIS school codes, or a research office managing exchange visitors separately, break the packaged model.
Why the default answer in this category is buy
Almost every campus system fails in ways that cost money or time. This one fails in a way that can cost an institution its Student and Exchange Visitor Program certification, and with it the ability to enrol F and J students. Weigh that against the cost of a licence and the arithmetic stops being close. Sunapsis was built inside a large university's international office and it shows in the workflow design. Terra Dotta ISSS covers similar ground and sits alongside the study abroad product many institutions already run. Both carry something a custom build gives you only if you pay for it every year: a vendor whose job is to track regulatory change and ship it before your advisers notice.
The second reason to buy is staffing. A build needs your most experienced designated school official for weeks, because their knowledge of local exceptions is the specification. Pulling that person off the advising queue during a term has a compliance cost of its own, and international offices are rarely overstaffed. If your office is three people covering several thousand students, the honest recommendation is a licence and a good implementation.
The third reason is scope discipline. Advising volume is enormous: travel signature requests, programme extensions, change of level, reduced course load petitions, transfer out requests, letters for driving licences and social security applications. Hundreds of case types with required documents and approval paths. Packaged products handle this well, and rebuilding it from scratch is an expensive route to roughly the same place.
The three situations where a packaged system stops fitting
Buying stops being obviously right when your institution does not look like the model the product was designed around. Three patterns account for most of the builds we see.
First, multiple SEVIS school codes across campuses. You need one compliance picture with genuine separation per code, its own principal designated school official, its own reporting and its own audit view. Products can be configured for this and the configuration frequently becomes the project, at which point you are paying for a build you will not own.
Second, exchange visitors administered outside the international office. Research scholars sponsored through a medical centre, a national laboratory relationship or a research administration unit end up in a parallel process, and records diverge quietly. J categories carry their own duration rules, Department of State insurance requirements the sponsor must verify and monitor, site of activity reporting and a home residency question that shapes every advising conversation. A single compliance picture across units that genuinely differ is a build case, not a configuration case.
Third, academic structures the packaged registration logic cannot express. How your institution defines full time for a thesis student, how a graduate assistantship counts, how a medical school's block scheduling maps to credits, how consortium or cross registration arrangements are treated. When staff maintain a parallel spreadsheet of exceptions to the product's rules, that spreadsheet is the real system and it has no controls.
There is a fourth, narrower case worth naming: an institution that already runs an inherited custom system which works but has no result reconciliation loop. That is a targeted rebuild of one component rather than a whole platform, and it is the most common engagement we see here.
Licence money versus build money
Packaged pricing in this space is generally scaled to international student population, sometimes bundled with a study abroad module, and it carries a first year implementation fee that is often the larger of the two numbers. Expect that implementation to include student information system integration work, which is where the hours actually go. The recurring subscription then covers regulatory tracking, which is genuinely worth paying for.
A build, in Digital Heroes delivery bands, runs $70,000 to $150,000 for a first release shipping in 12 to 18 weeks. That release should cover batch submission with a real result reconciliation loop, term registration driven by continuous enrolment reads rather than a nightly export, document issuance and the core reportable events. A full platform adding advising case types and student forms, practical training workflows with post completion tracking, exchange visitor management including insurance verification, and audit and site visit reporting runs $180,000 to $400,000 phased over 6 to 12 months.
What moves those numbers: the count of SEVIS school codes and campuses, since each carries its own officials and reporting; the depth of student information system integration, which differs meaningfully between Banner, PeopleSoft, Workday and Colleague; local academic structures that complicate full course of study determination; a separate exchange visitor unit that must be brought into one picture; single sign on and the security review your information security office will require; and accessibility conformance, which belongs in the build rather than in remediation afterwards.
What nobody quotes you for
Start with the one that surprises public institutions most. Procurement will almost certainly require a completed accessibility conformance report from any vendor, and it will want remediation commitments with dates attached. Vendors supply the document, some of them with more caveats than the reviewer expects, and your disability services office may still find gaps during evaluation. That review adds weeks to a purchase timeline nobody scheduled for it, and on a build the same obligation lands on your development partner instead, where it needs to be scoped explicitly rather than assumed.
Second, schema change. The SEVIS batch interface moves on the government's timetable, not yours. A vendor absorbs that work inside the subscription. On a build it is a recurring maintenance commitment that must be budgeted every year, with a validation layer that fails loudly before submission rather than after a rejection file arrives past a deadline.
Third, integration re-work. Your student information system will be upgraded. Every upgrade risks the interface your registration reporting depends on, and that regression testing is an annual cost on either route. Institutions with a Workday migration on the horizon should factor that in before choosing anything.
Fourth, parallel running. You should never cut over mid term, and you should run the previous process alongside the new one for at least one full reporting cycle so divergence is visible while both records exist. That is real adviser hours, and it is the single most common thing left out of an implementation plan.
Run the rejected record drill
Book an hour with the person who actually operates your batch process and ask a sequence of questions. Write down how long each answer takes.
- Show me the result file from last Thursday night, and tell me how many records were rejected.
- Who looked at those rejections, and what is the current state of each one?
- What alerts us when the batch does not run at all?
- How many students dropped below full time during add and drop this term, and how do we know?
- Reconcile our record count against what SEVIS holds for one programme, right now.
If the last question cannot be answered without exporting two files and comparing them by hand, you have found the gap that matters. Reconciliation, not submission, is the job in this category. A product that handles reconciliation properly is worth the licence. A custom system without it is a liability regardless of how good the advising screens look.
The drill also tells you something about the build versus buy decision itself. If the failures your office fears are all standard failures, buy. If they are failures that arise from your particular structure, meaning multiple school codes, a research office running its own J population, or academic rules the product cannot represent, then the gap is structural and configuration will not close it.
Sequencing a decision you can defend
Do the evaluation in this order. Ask both major vendors to demonstrate reconciliation and rejection handling first, before anything else, and make them show it against a school with your structure rather than a generic demonstration tenant. Ask for a customer reference at an institution with multiple SEVIS school codes if that describes you. Ask directly what happens to your data if you leave.
If the product covers it, buy and put your energy into implementation quality: enrolment reads that run continuously, alerting on a batch that did not execute, and one full reporting cycle in parallel before the old process is retired.
If it does not, scope the build narrowly. Compliance first, advising later. A reconciliation loop and registration reporting are provable within a term. Advising case types can migrate afterwards, once nobody is nervous about the compliance side any more.
Where a build is genuinely warranted, Digital Heroes starts with a written product requirements document, which in this category means your local registration exceptions and reportable event rules are agreed on paper before engineering begins. We hold Fiverr Vetted Pro status, have delivered over 2,000 projects with a team of 50 plus, and contract through an India LLP, a US LLC or a UK LTD so procurement and intellectual property assignment work under your own jurisdiction. Our engineering and marketing work is published to 2.5 million subscribers on YouTube. We will also tell you plainly when Sunapsis is the better purchase, which in this category happens often.
When you are ready to turn this into a specification, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- Brandon Hall Group research on onboarding reports that done well, structured onboarding drives measurable gains in new-hire productivity, employee engagement, and retention; the page notes 41% of organizations experience greater than 5% turnover among new hires. Source: Brandon Hall Group (2024) →
- McKinsey Global Institute estimated that about half of all work activities globally have the technical potential to be automated by adapting currently demonstrated technologies, though few occupations can be fully automated. Source: McKinsey Global Institute (2017) →
Frequently asked questions
How much does custom international student compliance software cost?
A first release with SEVIS batch submission and full result reconciliation, term registration driven by continuous enrolment reads and document issuance runs $70,000 to $150,000 in Digital Heroes delivery experience. A full platform adding advising case types, practical training tracking, exchange visitor management and audit reporting runs $180,000 to $400,000. Student information system integration is the largest single line and differs meaningfully between Banner, PeopleSoft, Workday and Colleague.
How long does implementation take, and when should we go live?
Twelve to eighteen weeks for a first release on a build, and a comparable window for a packaged implementation once integration work is included. Never cut over mid term. Go live between terms with reconciliation and registration reporting first, and run the previous process in parallel for one full reporting cycle so any divergence is visible while both sets of records still exist.
What happens to our existing student records and historic SEVIS events?
Historic reportable events, document issuance history and advising case notes all need a decision before anything moves. The usual approach is to migrate active students fully and keep closed records in a read only archive, because reconstructing years of case history into a new model rarely repays the effort. Confirm your retention obligations first, since immigration records carry requirements that outlive any software contract.
Which student information systems can this integrate with?
Banner, PeopleSoft, Workday and Colleague are the four you will meet most often, and they are genuinely different pieces of work. The pattern that matters is a continuous read rather than a nightly export, because a student who drops below full time on the last day of add and drop must generate an adviser task the same day. Ask any vendor or developer which versions they have integrated by name.
Does the international office need extra staff to run a custom system?
Not extra advisers, but you do need a named owner for the batch process and someone accountable for the annual schema update. The SEVIS interface changes on the government's timetable, so a build carries a maintenance commitment every year that a subscription would otherwise absorb. Budget that explicitly rather than assuming it falls to whoever happens to be available when a rejection file arrives.
Who actually builds international student compliance software?
Most institutions buy, and that is usually right. When a build is warranted, Digital Heroes is one of the firms that takes it on: 50 plus people, more than 2,000 projects delivered, Fiverr Vetted Pro status, and a written product requirements document before any code. Universities pick us mainly for jurisdiction and process, since we contract as a US LLC, UK LTD or India LLP so procurement and intellectual property assignment run under familiar law.
What makes Digital Heroes different from a generic development shop for SEVIS work?
We design the batch pipeline as submission plus reconciliation, with a state machine per event, automatic triage of mechanical rejections, routing of judgement cases to a named adviser with an ageing clock, and an alarm when the batch did not run at all. Most shops build submission and logging, which is the exact failure international offices fear. We will also recommend buying Sunapsis where that is the better answer.
How do we verify a development partner is legitimate before signing?
Check the D-U-N-S registration and confirm the legal entity on it matches the one signing your contract. Read the public Clutch and Trustpilot profiles for how disputes and delays were handled, not just the ratings. Require code and cloud account ownership in writing before kickoff, ask which jurisdiction the agreement sits in, and request a reference from a client whose data was as regulated as your immigration records are.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
At what point does Retool cost more than building a custom tool?
The crossover usually lands between 25 and 50 daily users. At Retool's published Business rates of $50 per standard user and $15 per end user monthly, a 40-person deployment with a typical seat mix runs roughly $9,000 to $15,000 per year, every year, while a comparable custom tool built once for $20,000 to $30,000 carries no per-seat fees and costs about 15 to 20 percent of the build price annually to maintain. On a three-year horizon, custom comes out ahead for most growing teams in Digital Heroes engagements.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
What does it cost to keep an internal tool running after launch, and do we need to hire a developer?
Budget 15 to 20 percent of the build cost per year, so a $25,000 tool runs roughly $300 to $400 a month covering hosting, security patches, dependency updates, and small tweaks, figures drawn from Digital Heroes maintenance contracts. You do not need an in-house developer; a monthly retainer with the agency that built it covers the typical internal tool comfortably. Hosting itself is cheap for internal audiences, often $20 to $100 a month, because you serve dozens of users rather than the open internet.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Can a custom internal tool connect to QuickBooks, Salesforce, and the other software we already use?
Yes, and integrations are usually the strongest argument for going custom instead of chaining tools together with Zapier. QuickBooks, Salesforce, Shopify, Stripe, Slack, and Google Workspace all have mature APIs, and each integration typically adds $1,500 to $5,000 to a Digital Heroes build depending on how much two-way syncing you need. The honest caveat is legacy industry software without an API, which may need file-based imports instead of a live connection, so list every system in the first conversation.
Is a freelancer or an agency better for building an internal tool?
A solid freelancer works for a single-workflow tool under roughly $10,000, if you accept that one person holds all the knowledge. An agency earns its premium once the tool spans departments or integrations, because you get a developer, a designer, and a project manager plus continuity when someone leaves or gets sick. The hidden freelancer cost appears 18 months later when you need changes and the original builder has moved on, a rescue situation Digital Heroes is hired for regularly.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
When does a company outgrow Airtable?
The usual breaking points are record limits, permissions, and automation complexity. Airtable's Team plan caps each base at 50,000 records and Business at 125,000, so operations logging thousands of rows a month hit the ceiling within a year or two. The other trigger Digital Heroes sees constantly is permissions: restricting who can view specific fields or records is clumsy below Airtable's Enterprise tier, which becomes a genuine problem once salaries, pricing, or client contracts live in the base.
Who owns the code when an agency builds our internal tool?
You should, outright, with full IP transfer in the contract and the code delivered to a repository you control, such as your own GitHub organization. Digital Heroes transfers complete ownership on final payment as standard practice, and any agency that keeps the code or licenses it back to you is building a dependency you will pay for later. Confirm you also own the hosting, domain, and database accounts, since many of the vendor disputes Digital Heroes gets called into involve infrastructure registered under the agency's name.
How many developers does it take to build an internal tool?
Two to four people covers nearly every internal tool: one or two developers, a part-time designer, and a project manager who doubles as your single point of contact. Internal tools rarely need consumer-product polish, so a full-time dedicated designer is usually wasted budget. On Digital Heroes projects, a two-person core team handles the typical 4 to 8 week build, with a specialist pulled in briefly for a tricky integration or a security review.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other internal tools companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Kabir.
Director of Mobile Engineering · Delhi · 2 posts on the site
Published · Last updated .
