↓ Skip to main content
  1. Home/
  2. What We Do/
  3. Software Development and Automation

Software Development and Automation

Fraze Marketing Agency serving Wylie, Allen, Plano, Garland, McKinney, Rockwall, Murphy, Sachse, Parker, Lucas, Lavon, Fate, Royse City, St Paul and Princeton.

  • In business since 2018
Table of Contents

Software is the other half of what we do. We build new tools from scratch, and we take on older code too, bringing it up to date rather than starting over when starting over is not needed. Let’s look at what you already have before anyone writes a line. The work runs remotely, so where your business is and how big it is do not matter.

We write in Python and plain JavaScript, connect systems through their APIs and n8n, and host on Cloudflare Workers. You get a fixed bid after the first call, before any work starts, and we stick to it. When the job ends, the code is yours.

What we build
#

Anything a business needs written. That can be an app that runs entirely in the browser, a service with its own API and stored data, or an automation that moves information between the systems you already use, so nobody has to copy it across by hand.

Two builds show the range. Fretboard Compass began as a Python and Flask web app and was rebuilt as plain JavaScript that runs in the browser, with no server at all. That is the retrofit side of the work: existing code moved to a new language and platform, with the same results. Hollowed Stone is the other side: a Cloudflare Workers app with its own game API, game state stored in Cloudflare KV, private games opened with an access code instead of an account, and an admin page behind Cloudflare Access.

What you get
#

  • Replace old code without losing what it did. The Fretboard Compass port had to match the Python version’s exported results exactly before it took over.
  • Get security findings fixed, not filed. Hollowed Stone’s review found 3 high and 2 medium issues, and all five were fixed in version 0.4.0.
  • Keep the rules where users cannot edit them. Hollowed Stone checks every move on the server with the same rules code the browser runs.
  • Keep hosting costs small where the job allows. Hollowed Stone runs on Cloudflare’s free tier, and Fretboard Compass needs no server.
  • Skip manual uploads. Both builds deploy from GitHub, and on Hollowed Stone a push to the main branch is live in about a minute.
  • Own the code outright. It is yours when the job ends, and we never resell work you hired us for.

How a job runs
#

A new enquiry gets an answer within one business day. The first call is a screen share: you show us the problem, the code or the tools you have now, and what they should be doing instead, and we work through it together.

Then you get a written scope: what gets built, what it replaces, and what we need from you to build it. The bid comes with it. Nothing starts until you have read both.

How pricing works
#

We bid the job, then we stick to the bid. The figure comes from the written scope, so you know the whole cost before any work starts. We publish no number here, because no two software jobs are the same size and a published figure would be a guess.

Who owns the code
#

You do. When the job ends, the code belongs to you. We may learn from what we built, but we will not resell the work you hired us for to anyone else.

“What if the job grows halfway through?”
#

The bid does not move. It covers the scope you read before work started, and if part of that scope turns out harder than we expected, the extra time is ours to absorb. That is why the scope comes first and the bid second: both of us know exactly what is being built before anyone names a price.

Frequently asked questions

How do you keep bugs out of the code?

With tests the new code has to pass before it replaces anything. When Fretboard Compass moved from Python to JavaScript, the Python version's results were exported as test cases, and the JavaScript version had to match every one before it went live. That suite now runs 157 tests. On Hollowed Stone, the same rules code runs in the browser and on the server, so the server checks every move a player makes.

How do you handle security?

We put security headers on every response and fix review findings rather than filing them. When a penetration tester reviewed Hollowed Stone, he found 3 high and 2 medium issues, among them a cross-site scripting hole and an API that took requests from any website. All five were fixed in version 0.4.0. Fretboard Compass runs a strict Content Security Policy that lets only its own scripts load.

Who maintains the software after it launches?

You decide, because you own the code when the job ends, so keeping it running never depends on us. Two things help whoever comes next: Fretboard Compass deploys from GitHub on every push and carries a 157-test suite, which lets the next person change the code and check that nothing broke.

What happens if the work runs late?

A delay on our side does not raise your price, because the bid is fixed. If the work takes longer than we planned, that time is ours to absorb, not yours to pay for. The written scope sets out what gets built before any work starts, so both of us are measuring progress against the same list.