Based in the Tampa Bay area Serving Florida and nationwide
Mon–Fri 8:00–6:00 Client Portal
PiTech Consultants
Our work

Live products, not mockups.

PiTech Consultants builds software people open every day, and then stays on it — updates, fixes, hosting and store submissions, for as long as it is in use. Every write-up below follows the same structure, so you can see the problem before the technology.

Client work

Commissioned by real clients, live, and still maintained.

Client work · Website + mobile app

St. Reweis Coptic Orthodox Church

One place for announcements, the weekly schedule and forms — on a phone and on the web — instead of separate systems that disagree with each other. Live on the App Store, Google Play and the open web.

The problem

The church needed a single home for announcements, the weekly schedule and its forms, and it had to be one that both members and ministry leads would actually use.

That meant it had to work properly on a phone and on the web at once — without anybody maintaining two disconnected systems and reconciling them by hand.

The workflow

The workflow that matters most is an announcement getting from the person responsible for it to every member who should see it:

  1. A ministry lead with announcement permission writes it
  2. Chooses the audience — the congregation, or a group
  3. Publishes now or schedules it
  4. It appears on the website and in the app at once
  5. Members get a notification on their phone or browser
  6. It expires on its own when it is no longer relevant

What we built

  • A website and a mobile app that match

    Same visual design across the web, iOS and Android, so moving between them does not feel like moving between two products.

  • One account, one shared database

    The same sign-in works on the website and in the app. Announcements and schedule changes made on either side update both, in both directions.

  • Permissions by task

    A member can be granted admin over one area only — announcements, the schedule or forms — or full super admin across everything.

  • Announcements and the weekly schedule

    Posted or edited on either platform, scheduled ahead of time if needed, and delivered as notifications.

  • Online forms

    Including multiple-choice questions, filled in from either platform, with responses exportable for the people who run them.

Screenshots

The St Reweis Church app home screen: the church name, the date in both calendars, and the readings for the day
App home — the day in both calendars, and its readings
The announcements list in the app, newest first, with some posts blurred
Announcements, newest first (some posts blurred)
The weekly schedule in the app, laid out day by day with start and end times
The weekly schedule, day by day
The Coptic calendar in the app, with a date picker and that day’s readings
Coptic calendar, with the readings for any date
The announcement composer an admin sees: a title field, a message with styling controls, photo and document attachments, the name it will be posted under, and a choice between sending to the congregation or to groups
The announcement composer (names blurred)

What someone with announcement admin actually gets: a title, a message with basic styling, photo and document attachments, the name members will see it posted under, and one choice of audience — the whole congregation, or a group.

Nothing is preselected there on purpose. An announcement reaches phones as a notification the moment it is published, and it cannot be unsent, so the screen makes you pick rather than picking for you.

Technology & integrations

Expo / React Native
One codebase for the iOS and Android apps.
Next.js
The website and its admin screens.
Supabase
Authentication and the shared database behind web and mobile, with row-level security enforcing the role permissions.
Push notifications
Mobile notifications through Expo, and web push for browsers.
Scheduled publishing
Posts queued by admins are published and announced on time by a scheduled job.
Exports
Form responses exported to PDF and CSV for the people who collect them.

Outcome

The site and the app are in daily use. Some of the people who were against the idea at the start are now among the ones using it.

New features and bug fixes are still being released.

What this demonstrates

  • One backend serving web and mobile, so nothing is entered twice.
  • Permissions scoped to a task, enforced in the database rather than only in the screens.
  • Notifications triggered by real events in the workflow.
  • A product maintained after launch, not handed over.

PiTech Labs

See what we can build.

PiTech Labs contains fictional product concepts, built to demonstrate how custom software can solve real operational problems. The businesses in them are invented; they are not client projects, and no client results are implied.

Field operations

FieldFlow

From lead to payment — one operational system.

A concept platform for field-service businesses that replaces disconnected spreadsheets, scheduling tools, job tracking, customer records and invoicing workflows with one custom application.

Explore FieldFlow Interactive demo

Capabilities

  • Job management
  • Scheduling & dispatch
  • Customer management
  • Estimates
  • Invoicing
  • Field documentation
  • Operational reporting

A fictional product concept. Not client work; no client results are implied.

In-house

Our own systems, held to the same standard.

Our own site · Website

The PiTech Consultants site

The one you are reading. It is here because a build standard is easier to inspect than to describe.

The problem

A firm that builds software is judged on its own site. This one had to load quickly on a phone, be findable in search, stay cheap to run, and be maintainable years from now — not by whoever remembers the page builder it was assembled in.

The workflow

The workflow it has to support is an enquiry reaching a person, reliably:

  1. A visitor fills in the contact form
  2. Bot protection and validation run on the server
  3. The enquiry is emailed to PiTech
  4. Only then is a confirmation sent back
  5. The visitor sees a real success or failure page

What we built

  • Custom design

    A small type and colour system rather than a purchased theme, so every page is consistent and nothing is fighting a template.

  • Pages from data

    Service and industry pages, cards, footer links and sitemap entries come from data files, so adding a page is one edit.

  • A contact form that cannot lose a lead

    Submissions handled server-side; the courtesy confirmation only goes out after the enquiry itself has been delivered.

Screenshots

The PiTech Consultants home page at desktop width
The home page at desktop width
The same PiTech Consultants home page at phone width
The same page at phone width

Technology & integrations

Astro
A static build: pages generated ahead of time and served as files.
Cloudflare Workers
Hosting, plus the one dynamic route — the contact form.
Turnstile and SendGrid
Bot protection and email delivery for enquiries.

Outcome

Live, hosted and maintained continuously — the same care plan a client site gets. Apart from bot protection on the contact form, no JavaScript is shipped to the pages people find in search, and there is no analytics or tracking on them.

Run any speed or accessibility tool over it; that is the standard on offer, and it is the one thing on this page you can check without asking anyone.

What this demonstrates

  • Performance and accessibility treated as requirements, not extras.
  • Content managed from data, so the site can grow without a rebuild.

Discuss your software idea.

Show us the workflow or the problem. We’ll tell you plainly what it would take — and whether custom software is the right answer at all.

Discuss Your Software Idea

You’ll hear directly from PiTech, typically the same business day.