Skip to main content

Web applications

Stop renting the software your company runs on.

Commerce, courses and customer portals built for how you sell. You own the code, the data and the cloud account.

Digital Potter builds custom web applications that replace rented software. We migrate everything you already have.

  • 12 weekstypical first release
  • 0records left behind
  • 100%of the code in your name
$48$62$36$54storefront$62.00$48.00$74.00total$184.00checkoutpaid#1042$184#1041$96#1040$212orders

Sound familiar?

Your store works. Running it does not.

Every new need means another app and another monthly fee. Orders live in one tool and students in another. Reports take a spreadsheet and an afternoon. Checkout looks like everyone else's. And when the platform changes its rules, you change your business.

  • Five or more paid apps holding the store together

  • Customers and orders split across tools

  • Fees that rise with every sale

  • A checkout you cannot change

storecoursesspreadsheetlegacy apporders 12,408lessons 214rows 48,770customers 3,920your platformone databaserecords65,312new platformorders12,408 = 12,408customers3,920 = 3,920lessons214 = 214rows48,770 = 48,770reconciliation0 records lost

What you get

A complete platform, not a theme on rented ground.

  • A storefront or portal designed for your customers

  • Payments with Stripe, in your own account

  • An admin your team can run from anywhere

    Products, orders, customers, courses and content in one place.

  • Every record migrated with a script we can re-run

  • Automated tests and a release pipeline from week one

  • Hosting in your cloud account, with monitoring, documentation and access handed over

Search rankings carry over. We map every old URL before cutover.

How it runs

Twelve weeks from first call to cutover.

The usual shape of a web build. Yours may be shorter.

  1. Map the store you have

    Week one

    Products, orders, customers, apps and fees, written down in one place.

  2. Agree on the first release

    Week two

    A fixed scope and a fixed number. Usually the store and the admin together.

  3. Build and migrate in parallel

    Weeks three to ten

    You use the new store in staging every week. The importer runs against real data the whole time.

  4. Cut over on a quiet day

    Weeks eleven and twelve

    Old URLs redirect, payments switch, and the old platform stays on until you are sure.

Not ready for a build?

Start with leadership instead.

  • Fractional CTO

    Decide what to build, what to keep and what to buy before you spend.

    Fractional CTO
  • Principal engineering

    A senior lead who runs your product engineering month to month.

    Principal engineering

A straight answer

When a custom build is the wrong call.

  • Your store is new

    Under a few hundred orders a month, a hosted platform is cheaper and faster.

  • The apps you rent still fit

    If nothing is held together with workarounds, keep what you have.

  • You need it live next month

    A real platform takes about twelve weeks. Anything faster is a template.

Investment

Builds from $35k.

You get a fixed number for the first release after the call.

  • recommended

    Web application build

    from $35k

    Storefront or portal, admin, migration and launch.

    • Fixed scope and price
    • Every record migrated
    • Code and cloud in your name
    • Launch support included

Questions

What owners ask about leaving a hosted platform.

  • Will we lose our search rankings?

    No, when it is done right. We map every old URL to its new home and set permanent redirects before cutover. Product and category pages keep their addresses where we can.

  • How do payments work, and who holds the money?

    Payments run through Stripe in your own account. The money goes straight to you. Card data never touches our servers.

  • What happens to past orders and customer accounts?

    They move with you. The importer brings over orders, customers and products, then we check totals against the old platform year by year.

  • Who hosts it after launch?

    It runs in a cloud account in your name. Our team sets up monitoring and can look after it monthly, or hand it to yours.

  • How long does it take?

    Most web builds take about twelve weeks from the first call to cutover. You use working software in staging from the first month.

  • Who owns the code?

    You do, from the first commit. It lives in your repositories.

Next step

Bring your list of monthly subscriptions.

In thirty minutes you learn which ones a platform of your own would replace. And roughly what it costs.