Services

Digital systems & software

Tools your staff can run.

Turn a workflow that lives in spreadsheets and inboxes into an application, integration or dashboard your team can maintain. Start with requirements; finish with documentation and an agreed support rhythm.

Hisham wrote Epic workflow and automation requirements in a county role.

Book a 20-minute call

How to start and how it is priced

Your first step: A process map and requirements brief
How it runs: A diagnostic, one priority deliverable, then a defined build or an agreed monthly rhythm.
How it is priced: After a 20-minute call, you receive a written quote for the first piece of work: the deliverable, review dates and one fee, based on the number of awards or records involved and the deadline. Ongoing work is priced as a fixed monthly fee for agreed capacity. No commission or contingency.
Before work begins: Software, specialist services and travel are listed separately. Work begins only after you accept the written scope and fee.
Next step: Start a conversation See how a first month works

Praxis brings in software engineers for specialist development and review. If a scope needs a specialist, Praxis names the person and the role in the written scope, and that person joins only with your approval.

Salesforce for the work behind fundraising

Hisham brings deep, hands-on Salesforce experience to nonprofit fundraising and operations. His work includes nonprofit configuration, donor records and campaigns, reports and dashboards, data cleanup and imports, automations and integrations.

Start with the records your staff use, the decisions they need to make and the reports they need to trust. A Salesforce engagement can include:

Reviewing donor and prospect records, data quality and follow-up workflows.
Configuring reports and dashboards around fundraising and program needs.
Planning data cleanup and imports, with validation and clear ownership.
Mapping gift and grant records to finance reporting and reconciliation.
Documenting configuration and training staff to maintain it.

Automation and integrations are scoped after reviewing your Salesforce setup, permissions and connected systems. Software engineers join where custom development or security-sensitive work requires them.

Discuss Salesforce and donor systems

Who this is for

Intake, referrals, awards or partner information scattered across tools.
Recurring reports that require days of copying and reconciling.
An internal IT team or vendor that needs precise requirements and acceptance tests.

Not included

Medical-device or other regulated engineering.
Patient-care systems or protected health information.
An unscoped 24/7 service or security assurance without qualified review.

Delivery stages

How the work unfolds.

Weeks 1 to 2

Map the work

Process map and data inventory
Requirements and acceptance criteria
Prototype of the highest-risk assumption

Weeks 3 to 6

Build and validate

Bounded application or integration
Staging review and acceptance tests
Training and handoff records

Ongoing

Maintain and improve

Issue triage during agreed hours
Updates and small enhancements
Quarterly roadmap and operating review

Deliverables

The work leaves something behind.

Your repository and agreed IP rights
Client-owned hosting and service accounts
A runbook, data map and acceptance record
A maintenance backlog and named response targets

Most engagements draw on one or two workstreams.

Workstreams and deliverables

Combine the workstreams your team needs, with clear owners and review points.

01Discovery and requirementsMake your workflow, users and acceptance decisions buildable.

Process maps in Visio or Whimsical
User, role and permission definitions
Data inventory with a source and owner register
Functional requirements and prioritized backlog
Acceptance criteria and representative test cases
Build-versus-buy comparison with operating costs and dependencies
Vendor evaluation matrix and technical request for proposals (RFP) support
Prototype of the highest-risk assumption before committing to a larger build

02Web applications and portalsDefine the smallest application that resolves the agreed operational problem.

HTML, CSS and JavaScript interfaces; React or a lighter framework when it fits the application
Node.js or Python application and API services within an agreed supported stack
PostgreSQL, SQLite or Supabase data structures, migration and ownership plan
Authentication, roles and account lifecycle requirements
Forms targeting Web Content Accessibility Guidelines (WCAG) 2.2 AA, including keyboard operation and tested error recovery
File-upload validation, storage rules and document-handling workflows
Notifications and template messages, with delivery and error handling
Administration screens and permissioned record editing
Client-owned hosting with Cloudflare, Vercel or Render considered against the operating requirements

03Intake, referral and case workflowsConnect collection, routing and follow-up without collecting information the workflow does not require.

Intake forms and field dictionary
Intake-to-tracker mapping and duplicate checks
Referral routing and assignment rules
Status dashboard and outcome-recording fields
Reminders, overdue-item queues and escalation rules
Consent-state and access-control requirements
Retention and deletion workflow under the client’s approved policy
De-identification requirements and exception handling, reviewed with the client’s responsible team

04Data and reportingMake the inputs and transformations behind a recurring report visible.

Data models and reporting definitions
Import and extract, transform and load (ETL) pipelines with source validation
Deduplication, matching rules and a manual-review queue
Looker Studio, Power BI, Metabase or custom dashboards selected against your reporting and licensing needs
Scheduled funder-report aggregation and formatting
Data-quality rules and an exception dashboard
Periodic reconciliation and quality-review checklist
Refresh ownership, lineage documentation and failed-job notification

05Integrations and automationConnect systems around an approved event, ownership rule and failure path.

REST API integrations and authentication requirements
Webhook intake, validation and duplicate-event handling
Customer relationship management (CRM) workflows across Salesforce, Airtable, DonorPerfect and Bloomerang, where account and API access allows
Finance workflows for QuickBooks Online and BILL, with reconciliations and approval boundaries
Google Workspace and Microsoft 365 workflows
Instrumentl, scheduling and Formspree integrations where the product supports the required interface
Zapier/Make automation versus Python-script comparison and scoped implementation
Scheduled jobs with retries, logging and failure notifications
Document generation for approved award-letter, invoice and reporting templates

06AI-assisted workflowsKeep source material, review responsibility and error tolerance explicit.

Document classification using approved, bounded examples
Structured extraction from invoices or applications with field-level validation
Retrieval over an approved policy or knowledge collection, with source references
Drafting assistants with a human approval step
Evaluation sets and acceptance thresholds agreed before rollout
Data-boundary, access and provider-retention requirements
Logging, exception queues and review of uncertain outputs
Pilot limitations, fallback workflow and deployment go/no-go record

07Websites and content systemsConnect publishing needs with accessibility, performance and maintainability.

Fast static sites using an agreed content and deployment workflow
WordPress maintenance and content architecture
Wix or Squarespace when the client’s ownership and editing needs favor them
Technical SEO, sitemap, canonical and metadata setup
Privacy-aware analytics configuration and measurement definitions
Accessibility review, remediation backlog and verification
Image and font optimization and page performance budgets
Editor documentation, redirects and content migration checks

08Enterprise coordinationTranslate program needs into requirements that fit the client’s IT governance.

Epic workflow and automation requirements coordinated through your authorized IT team
Program-to-IT process and dependency maps
Engineering tickets with data fields, routing rules and acceptance criteria
Security-review input and remediation tracking
Change-request packages and release coordination
Procurement and vendor requirements and decision records
User-acceptance testing coordination and issue triage
Training, operating documentation and ownership handoff

09Delivery and controlsSpecify the engineering standard in the contract and assign qualified owners.

Client-owned Git/GitHub repository, branch protection and review workflow
Separate staging and production environments
Acceptance criteria, test plan and release checklist
Continuous integration appropriate to the application
Secrets management and least-privilege access design
Backup policy, restore test and rollback procedure
Uptime and error monitoring with a named response route
Runbook, architecture notes and handoff documentation
Defined support hours, response targets, maintenance cadence and prioritized roadmap
Qualified specialist ownership of security-sensitive implementation and review

Experience behind the work

County role

Epic workflow and automation requirements

Hisham developed Epic workflow and automation requirements that connect program needs with technical delivery.

Read the work

Tools Hisham has worked in

Examples include Epic workflow requirements, SQL data models and API integrations. Access and implementation needs are agreed for each scope.

Finance systems and experience are listed on Finance & award administration.

Epic · APEX: workflow design and automation requirements (county role)
Microsoft 365 · Google Workspace: team collaboration
Microsoft Visio · Asana: process mapping and project coordination
GitHub: version control and delivery collaboration
WordPress · Wix · Squarespace: website development and maintenance
APIs · Workflow automation: connected applications and reliable handoffs
HTML/CSS · JavaScript: web development, application logic and data
SPSS · R · Stata · SAS · Python · SQL: Statistical analysis, data preparation and reporting support

Start a conversation

Questions

Common questions

Who owns the code and accounts?

Your scope identifies the repository, hosting accounts, deliverables and IP rights. New accounts are created in your name or transferred as agreed. Third-party and open-source components keep their own licenses.

Will you work with our IT department?

Yes. Your IT team sets its access, architecture, security and change-control requirements. Praxis translates program needs into tickets, field definitions, routing rules and test cases that fit that process.

How do you handle security and data?

Praxis defines data boundaries and access roles before development. Credentials stay in approved secret stores; releases include review and rollback plans.

What does hosting cost?

You receive the expected hosting, software and maintenance costs with the scope. Praxis compares existing tools with a new build and flags paid tiers, usage-based charges and vendor dependencies before you commit.

What happens after launch?

A maintenance retainer can cover issue triage, updates, backups, small enhancements and a prioritized roadmap. Response targets and support hours are written down. A one-time delivery ends with the agreed handoff.