EXECUTIONSOFT / OUR WORK

Our projects.

Projects we've worked on and built.

• </> 01

  Deli Spices

  A food recipe quality-control application.

  Proposed capabilities — draft scope

  The capabilities below describe what this type of application could support. They are proposals for discussion, not a list of confirmed or implemented Deli Spices features.

  01 / Recipe & formulation management

  • Maintain a controlled recipe library with ingredient quantities, units, preparation instructions, expected yields, and product specifications.
  • Scale formulations to a target batch size with unit conversion, rounding rules, and checks that ingredient proportions remain consistent.
  • Record recipe revisions, reasons for changes, effective dates, and approval status so production can use the correct released version.

  02 / Ingredients & supplier quality

  • Catalog raw materials, approved suppliers, supplier specifications, storage conditions, and ingredient substitution restrictions.
  • Capture incoming deliveries, supplier lot numbers, expiry or best-before dates, inspection results, and certificates of analysis.
  • Track accepted, quarantined, or rejected materials and prevent unapproved ingredients from being selected for a production batch.

  03 / Batch execution & production records

  • Create batch records tied to an approved recipe revision, planned quantity, production location, equipment, and responsible operators.
  • Record actual ingredient weights and lots, processing steps, timestamps, and deviations from the planned formulation.
  • Compare expected and actual yields, document waste or rework, and retain the production history for each finished batch.

  04 / Quality specifications & inspections

  • Define product-specific inspection plans with sampling frequency, test methods, measurement units, and approved acceptance limits.
  • Capture relevant checks such as weight, moisture, pH, temperature, particle size, or blend uniformity, depending on the product.
  • Compare results against the applicable specification, flag out-of-range readings, and require review of missing or failed checks.

  05 / Sensory evaluation & consistency

  • Use structured scorecards for appearance, color, aroma, flavor, texture, and other product-relevant attributes.
  • Compare samples with an approved reference, recording evaluator identity, evaluation conditions, scores, and observations.
  • Review batch-to-batch trends to identify variation and support recipe or process investigations.

  06 / Allergen & labeling controls

  • Maintain supplier-declared allergen information and calculate recipe-level allergen declarations from the selected ingredients.
  • Flag formulation or supplier changes that require label review, including ingredient statements and potential cross-contact concerns.
  • Record packaging and label-version checks, with qualified review before release; calculated information would not replace verified supplier data or testing.

  07 / Food-safety monitoring & laboratory results

  • Support monitoring records defined by a qualified team's food-safety plan, including relevant process controls and corrective actions.
  • Attach laboratory reports and microbiological or chemical test results to samples and batches, preserving methods, dates, and review status.
  • Record sanitation verification and equipment calibration checks where required by the production workflow.

  08 / Holds, approvals & batch release

  • Track batches through draft, in-production, awaiting-review, on-hold, released, or rejected states with controlled transitions.
  • Require completion of the applicable checks and authorized quality review before recording a release decision.
  • Preserve reviewer identity, decision time, supporting evidence, and reasons for rejection or any authorized exception.

  09 / Nonconformance & corrective actions

  • Log failed inspections, formulation errors, complaints, and process deviations against the affected recipe, material, or batch.
  • Assign investigation owners, containment actions, root-cause findings, due dates, and corrective or preventive actions.
  • Document approved disposition, such as rework or rejection, and verify action effectiveness before closing an issue.

  10 / Traceability & recall support

  • Link supplier lots to ingredient usage, production batches, finished-product lots, and dispatch records when available.
  • Trace backward to source materials or forward to potentially affected products and recipients during an investigation.
  • Generate traceability reports for mock recalls and incident response, including quantity reconciliation and documented follow-up.

  11 / Storage & shelf-life records

  • Track storage locations, stock status, expiry dates, and first-expiring-first-out selection for suitable materials.
  • Record storage-condition readings and excursions, with review of any potentially affected ingredients or finished goods.
  • Schedule retained-sample reviews and shelf-life study checkpoints; expiry recommendations would require validated study evidence.

  12 / Dashboards & reporting

  • Summarize pending inspections, held batches, overdue actions, and upcoming material expirations for each responsible team.
  • Analyze rejection rates, yield variance, recurring defects, and supplier-quality trends with filters by product and date.
  • Export reviewed batch summaries and quality reports with the underlying specifications and results for context.

  13 / Access control & audit history

  • Separate permissions for recipe authors, production operators, quality reviewers, and administrators.
  • Retain attributable changes, previous values, timestamps, and reasons for edits to controlled records.
  • Define record retention, backup and recovery, and document access policies appropriate to the business.

  14 / Integrations & data capture

  • Explore barcode scanning for material and batch identification, with validation to reduce incorrect lot selection.
  • Connect compatible scales, laboratory systems, inventory tools, or ERP platforms where interfaces are available.
  • Validate imports, handle duplicate or missing records, and reconcile integration failures rather than silently accepting incomplete data.

  Illustrative workflow

  Approve a recipe → inspect incoming ingredients → create a batch → capture production and quality checks → investigate exceptions → authorize release → retain traceability and reporting records.

  Scope & validation boundaries

  Actual functionality, integrations, test limits, and approval rules would need confirmation. Food-safety controls must be defined and validated by qualified professionals for the relevant products and jurisdiction. Software alone does not establish product safety, regulatory compliance, or certification.

• </> 02

  MyAgBuddy

  An application for farmers to monitor soil moisture, temperature, and nutrients.

  Proposed capabilities — draft scope

  The capabilities below describe what this type of application could support. They are proposals for discussion, not a list of confirmed or implemented MyAgBuddy features.

  01 / Farm, field & crop management

  • Organize farms into fields, management zones, and monitoring locations, with boundaries and location references.
  • Record crop varieties, planting dates, growth stages, soil types, and irrigation systems to give readings agricultural context.
  • Retain seasonal records so farmers can compare conditions within a field and across growing seasons.

  02 / Sensor setup & connectivity

  • Register compatible probes and gateways against a field, installation depth, and geographic location.
  • Configure supported sampling and upload intervals, recording device identity, measurement units, and installation dates.
  • Display battery levels, connectivity, and last-received timestamps so a disconnected sensor is not mistaken for a healthy field.

  03 / Soil moisture monitoring

  • Track moisture readings at relevant root-zone depths, distinguishing volumetric water content from soil-water tension where supported.
  • Compare readings with field-specific reference ranges established for the soil, crop, growth stage, and measurement method.
  • Show drying and wetting patterns after irrigation or rainfall, highlighting conditions that may warrant inspection for water stress or excessive moisture.

  04 / Soil temperature monitoring

  • Record soil temperature by location and depth with clearly identified Celsius or Fahrenheit units.
  • Review daily minimums, maximums, and trends alongside crop-stage context to support planting and field-management discussions.
  • Flag sustained readings outside user-defined ranges without treating a single measurement as a diagnosis of crop damage.

  05 / Nutrient measurements & soil tests

  • Record nutrient results such as nitrogen, phosphorus, and potassium from compatible validated instruments or laboratory soil tests.
  • Preserve sample date, depth, location, analytical method, nutrient form, and units; distinguish measured values from estimates and manual entries.
  • Compare results only when their methods and units are compatible. Electrical conductivity is not a direct measurement of individual nutrient concentrations.

  06 / Calibration & data quality

  • Maintain calibration records, maintenance schedules, and soil-specific corrections where recommended by the equipment manufacturer.
  • Flag missing, stale, implausible, or abruptly changing readings for review while preserving the original observations.
  • Show quality flags and measurement limitations, and support comparisons with field samples or reference instruments.

  07 / Field dashboards & maps

  • Present the latest available moisture, temperature, and nutrient information with timestamps and device status.
  • Map monitoring points and compare zones without implying that a single probe represents an entire field.
  • Clearly label interpolated or estimated map layers and expose the observations used to generate them.

  08 / Thresholds & farmer alerts

  • Configure field-specific alerts for moisture, temperature, nutrient-test results, low batteries, and missing sensor updates.
  • Use persistence windows and repeat-notification controls to reduce alerts caused by short-lived fluctuations.
  • Route notifications through supported channels, recording delivery status, acknowledgments, and follow-up actions.

  09 / Irrigation decision support

  • Review root-zone moisture trends alongside crop needs, soil properties, recent irrigation, and rainfall records.
  • Record irrigation timing, duration, and applied volume when known, then review the observed soil response.
  • Offer explainable prompts for farmer review rather than assuming automatic valve control or prescribing a universal watering schedule.

  10 / Nutrient planning & application records

  • Combine reviewed soil-test results, crop requirements, and historical applications to support discussions with an agronomist.
  • Log fertilizer products, nutrient composition, application dates, rates, treated areas, and the units used.
  • Track follow-up sampling and observations; any application recommendations would require locally appropriate agronomic validation.

  11 / Weather & historical trends

  • Explore integrations with compatible weather stations or forecast services, identifying their source and update time.
  • Overlay rainfall and air-temperature records with soil trends to help explain changes rather than assume their cause.
  • Compare periods and seasons while keeping forecasts, measured observations, and missing-data intervals visually distinct.

  12 / Mobile fieldwork & limited connectivity

  • Provide mobile-friendly field views and capture notes, photos, sample references, and maintenance observations.
  • Explore offline access to previously synchronized records and queued field entries for locations with unreliable connectivity.
  • Label cached readings with their age, reconcile synchronization conflicts, and explain that remote alerts depend on successful data delivery.

  13 / Reports & agricultural integrations

  • Export field histories, sensor readings, laboratory results, and irrigation or fertilizer logs for farmer and adviser review.
  • Summarize trends and data coverage by field, depth, and season without claiming unverified yield or resource savings.
  • Explore farm-management and laboratory integrations with validated units, source attribution, and handling for duplicates or failed imports.

  14 / Team access & farm-data protection

  • Separate permissions for farm owners, field workers, agronomists, and administrators, with access limited to authorized farms.
  • Record changes to thresholds, device assignments, and field records, including who made each change and when.
  • Define secure device credentials, controlled data sharing, retention, export, and backup-and-recovery policies.

  Illustrative workflow

  Register a farm and its fields → install and calibrate compatible sensors → collect soil readings and test results → review trends and quality flags → investigate alerts → record farmer-approved actions → compare follow-up observations.

  Scope & validation boundaries

  Actual hardware support, connectivity, measurement accuracy, integrations, and functionality would need confirmation. Soil readings depend on sensor placement, depth, calibration, soil properties, and sampling methods. Nutrient interpretation and irrigation or fertilizer decisions should be reviewed with a qualified agronomist using local conditions and validated soil tests. Monitoring alone does not guarantee improved yields, reduced input costs, or environmental compliance.

• </> 03

  WRAPP Technologies

  A mobile application for on-demand waste removal, using an Uber-style booking model.

  Proposed capabilities — draft scope

  The capabilities below describe what this type of application could support. They are proposals for discussion, not a list of confirmed or implemented WRAPP Technologies features.

  01 / Customer accounts & pickup requests

  • Let households and businesses create profiles, manage contact details, and save collection addresses.
  • Request waste removal from a mobile device, selecting a pickup location and providing access instructions.
  • Review booking details and service terms before submitting a request, with a reference number for follow-up.

  02 / Waste classification & load details

  • Describe waste using supported categories, item counts, estimated volume or weight, and optional photos.
  • Capture collection constraints such as stairs, bulky items, loading access, and whether additional crew or equipment may be needed.
  • Screen for prohibited or restricted materials and route uncertain requests to review rather than assume all waste can be collected.

  03 / Service areas & scheduling

  • Check whether a pickup address falls within an active service area before offering booking options.
  • Offer on-demand requests or scheduled collection windows according to collector availability and capacity.
  • Support rescheduling and, where appropriate, recurring business collections with clear cutoff and cancellation rules.

  04 / Estimates & transparent pricing

  • Calculate an estimate from supported pricing inputs such as load size, waste category, travel, labor, and disposal charges.
  • Identify whether a price is fixed or estimated, with an itemized explanation of fees and applicable taxes.
  • Require customer approval of documented price changes when the actual load differs from the original request.

  05 / Collector onboarding & eligibility

  • Register collection businesses, drivers, vehicles, service areas, and supported waste categories.
  • Collect relevant permit, insurance, and vehicle documentation for review, with expiry reminders where required.
  • Restrict job eligibility by verified capability, vehicle capacity, and service requirements; uploading a document would not itself establish authorization.

  06 / Matching & dispatch

  • Offer requests to eligible nearby collectors based on availability, waste-handling capability, and suitable vehicle capacity.
  • Use controlled acceptance and assignment steps so two collectors cannot independently accept the same job.
  • Handle declined, timed-out, or unassigned requests with reassignment or operator review and customer updates.

  07 / Driver workflow & navigation

  • Provide a mobile job queue containing the pickup address, load description, collection window, and access notes.
  • Record progress through accepted, en route, arrived, collecting, and collected states, with timestamps and exception reasons.
  • Explore navigation links and route planning for compatible mapping services, without encouraging interaction while driving.

  08 / Location tracking & arrival estimates

  • Show the assigned collector's latest available location during the active job, subject to device permissions and connectivity.
  • Present arrival estimates with update times, distinguishing estimated arrival from a guaranteed collection time.
  • Limit location sharing to the relevant booking and mark stale updates rather than presenting old positions as live tracking.

  09 / Notifications & communication

  • Notify customers about acceptance, collector arrival, schedule changes, collection completion, and payment status.
  • Offer supported in-app messaging or privacy-conscious contact options for clarifying access and load details.
  • Record delivery status and communication history, with escalation paths when a customer or collector cannot be reached.

  10 / Collection evidence & disposal records

  • Capture pickup timestamps, item or load confirmation, and appropriate before-and-after photos or customer acknowledgment.
  • Link collections to destination facilities, transfer records, weighbridge tickets, or disposal receipts where available.
  • Distinguish proof of collection from proof of lawful disposal; record recycling or recovery outcomes only when supported by evidence.

  11 / Payments, receipts & collector payouts

  • Explore payment-provider integrations for approved collection charges, using provider-managed payment details rather than storing raw card data.
  • Track authorization, capture, failed payments, refunds, and receipts while preventing duplicate charges during retries.
  • Reconcile collector earnings, platform fees, and payouts under agreed commercial terms and provider requirements.

  12 / Cancellations, disputes & feedback

  • Handle customer cancellations, collector no-shows, inaccessible properties, and unsuitable loads with documented reasons.
  • Support review of pricing disputes, service complaints, and refund requests using booking and collection evidence.
  • Collect feedback from completed bookings, with moderation and an opportunity to investigate reported problems.

  13 / Operations dashboards & reporting

  • Give authorized operators visibility into pending bookings, active jobs, unassigned requests, and service exceptions.
  • Report on collection volumes, response times, cancellations, and financial reconciliation with clear definitions and data sources.
  • Explore business-account exports and fleet or facility integrations without claiming unverified environmental savings.

  14 / Privacy, security & mobile reliability

  • Separate customer, driver, collection-business, and administrator permissions, limiting access to relevant jobs and records.
  • Protect addresses, location history, photos, and contact details with appropriate access controls and retention policies.
  • Handle interrupted connections, queued updates, and synchronization conflicts while preserving an attributable history of booking changes.

  Illustrative workflow

  Describe the waste and pickup location → review an estimate and collection window → match an eligible collector → follow job progress → approve any load or price changes → record collection evidence → process payment → retain disposal records and feedback.

  Scope & validation boundaries

  Actual functionality, platforms, service regions, pricing, integrations, and collector arrangements would need confirmation. Waste categories, transport permissions, handling procedures, and destination requirements depend on local regulations and appropriately authorized operators. Hazardous or restricted waste would require specialist review and must not be treated as an ordinary pickup. An Uber-style booking model describes the service concept, not an affiliation or integration with Uber. Software alone does not guarantee collector availability, lawful disposal, or environmental compliance.