Skip to content
Georgia · Agentic SaaS development

SaaS Development for Founders in Georgia

For a SaaS founder in the US state of Georgia, the first sales tax question is partly answered on the invoice. A Department of Revenue rule says software delivered electronically is not subject to the state's sales or use tax, but only if the invoice, contract or other documentation states the delivery method. Leave it out and the Department presumes delivery on a tangible medium, and you then have to prove electronic delivery.

Curiosive works from Ankara, Türkiye, and builds SaaS with AI coding agents, with a senior engineer reviewing every change. Agents produce the CRUD screens, admin views, migrations and test suites. Engineers design the multi-tenant data model, tenant isolation, plan and entitlement logic and the billing webhooks, because those are where a subscription product quietly loses money or leaks data between customers.

24
published portfolio projects
5+
years building for production
12
countries the work runs in
100%
of code read by a senior engineer
1 day
to hear back, from the engineer

For US founders and product teams

A US company. An engineering partner you can keep.

Curiosive LLC is our US-registered company. Engineering is led from Ankara, Türkiye, with collaboration across European and US time zones. Your engagement starts with a written scope, monthly capacity and a clear delivery plan.

Know who you hire

Curiosive LLC provides the services. Our US company details and service terms are published, and pricing is in USD.

Know what will ship

Agree scope, capacity and start date before checkout. Work through a prioritized queue, with senior engineers reviewing changes before they reach production.

Keep ownership

Typed, tested and documented code, with no lock-in to our tooling. Define repository access, handover and the working-hour overlap during discovery.

Georgia sales tax on SaaS and software subscriptions

Rule 560-12-2-.111 is the starting point: computer software delivered electronically is not a sale of tangible personal property, provided the paperwork says how it was delivered. For a subscription product that turns the invoice template into a tax control, so the delivery method belongs in the invoice and contract templates the billing system generates, not in someone's memory. Rates still matter if anything you sell is taxable, such as a device. The Department's rate chart effective October 1, 2026 includes the 4% state rate in every jurisdiction except two special Fulton codes (803 and 805), with combined rates of 8.9% in the Atlanta portions of Fulton and DeKalb counties and 6% in Cobb and Gwinnett counties. Other states set their own rules; California's SB 122 subjects SaaS to sales and use tax from January 1, 2027, so a product sold nationally needs per-state tax logic.

Georgia economic nexus rules for remote SaaS sellers

Since South Dakota v. Wayfair, decided June 21, 2018, physical presence is no longer the test for whether an out-of-state seller has to collect sales tax. Georgia's version is Department of Revenue Policy Bulletin SUT-2019-02. From January 1, 2020, a remote seller must collect and remit state and local sales tax if, in the previous or current calendar year, it had more than $100,000 in gross revenue from retail sales of tangible personal property delivered into the state, or 200 or more separate such sales. The original threshold, from January 1, 2019, was $250,000. The test counts tangible personal property, so a SaaS company that also ships hardware, kits or physical media should track those sales by destination from day one, in a report built on a data model an engineer has defined.

Selling SaaS to Georgia state agencies: US-only data and access

Public sector buyers bring their own hosting rules. The Georgia Technology Authority's standard SS-15-002 on data location and access, revised June 1, 2022, requires all State data to be processed, stored, transmitted and disposed of within the United States, and it explicitly covers SaaS and other cloud providers hosting State data. It also bars access to state agency systems and data from outside the US without an approved exemption from the GTA Office of Information Security. Because our engineers work from Türkiye, a project like this has to be set up around that rule: the product is built and tested on non-State data, deployed to US regions on hosting accounts in your name, and production access to State data stays with your own people in the US unless an exemption is approved. Better to know that before the tender than after it.

Georgia's fintech cluster and SB 540 chatbot exclusions for SaaS

The Georgia Department of Economic Development reports over 260 fintech companies in the state as of 2025, about 170K tech jobs as of 2025 and $44B of state GDP from IT in 2024. It says Atlanta is called 'Transaction Alley' for its payment processing firms and names health IT, cybersecurity and gaming as strengths. For SaaS teams adding an AI assistant, Georgia's companion chatbot law (SB 540, effective July 1, 2027) matters mostly for what it excludes: generative AI used only for a business's internal purposes, systems built and marketed mainly for software development, research, technical assistance or enterprise productivity, and customer-service chatbots that either do not sustain a relationship across multiple interactions or are not designed to elicit emotional attachment. A B2B workflow assistant may fall on the excluded side, but its design decides it.

Multi-tenant SaaS architecture built with coding agents

Tenant isolation is designed by an engineer before agents write a single screen, because retrofitting it means reviewing nearly every query. Billing follows one rule: the payment provider's events are the source of truth, and webhook handlers are idempotent, so a redelivered event is not processed twice. Plans and entitlements live in one place that every part of the product reads. Agents then produce the CRUD screens, admin views, migrations and test suites around that core, and a senior engineer reviews each diff. Reveal Software (reveal.software) is built with Hono, Drizzle ORM and PostgreSQL, and PicKey (pickey.ai) has Stripe subscription billing. A billing fault reported in a Georgia afternoon reaches us at the start of the next Ankara day, which is still night for you, so alerting and event replay belong in the first release.

Questions

The things people ask before starting.

Is SaaS subject to sales tax in Georgia?

Not under the rule for electronically delivered software, provided the invoice or contract states the delivery method; when documentation is silent, the Department presumes tangible delivery. How a specific hosted subscription maps onto that rule is worth confirming with an accountant, especially if you also sell anything physical, which can be taxable at combined rates such as 8.9% in the Atlanta portions of Fulton and DeKalb.

What is the economic nexus threshold for remote sellers in Georgia?

More than $100,000 in gross revenue, or 200 or more separate sales, of tangible personal property delivered into the state in the previous or current calendar year. That threshold has applied since January 1, 2020, replacing the original $250,000 figure from 2019, under Department of Revenue Policy Bulletin SUT-2019-02.

Can SaaS for Georgia state agencies be hosted outside the US?

No. GTA standard SS-15-002 requires State data to be processed, stored, transmitted and disposed of within the United States, and it names SaaS and cloud providers explicitly. Access to state systems and data from outside the US also needs an approved exemption from the GTA Office of Information Security, which affects offshore engineering and support.

Does SB 540 cover a support bot in my B2B SaaS?

Probably not, if it fits the exclusions. SB 540 leaves out customer-service chatbots that do not sustain a relationship across multiple interactions or are not designed to elicit emotional attachment, plus systems built mainly for enterprise productivity or technical assistance. A bot designed as an ongoing companion is a different case.

How it starts

What happens after you write to us.

  1. 01

    You describe the product

    One paragraph on what you are building, roughly when you need it, and who it is for. No brief, no form with fifteen fields.

  2. 02

    You get a reply within a day

    From the engineer who would do the work, not a sales team. If we are not the right fit we say so, and where possible we point you somewhere better.

  3. 03

    You get a scoped plan

    Scope, price and timeline in writing before anything is committed. You decide with the numbers in front of you.

No long contract to begin, no lock-in to our tooling, and the code is yours from the first commit.

Start a conversation
Contact

Looking for an engineering partner for the long haul?

A short note about the product, the timeline and who it is for is enough to start. You will hear back from the engineer who would do the work, not a sales team.

Ankara / Türkiye · Working across European and US time zones