25.10.2013 Views

Automation of SACCOs - FSD Kenya

Automation of SACCOs - FSD Kenya

Automation of SACCOs - FSD Kenya

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

AUTOMATION OF SACCOS: ASSESSMENT OF POTENTIAL SOLUTIONS • 55<br />

ID opportunity Benefit obstacle Change requirement System requirement<br />

5 Use historic loan performance Cost effective marketing. Not applicable. Capture data about<br />

The GL needs to<br />

and cost per acquisition to<br />

target marketing activities.<br />

Manage which type <strong>of</strong><br />

customers are acquired<br />

marketing activities such<br />

as marketing channel,<br />

target customer type<br />

capture financial data<br />

with sufficient detail<br />

including cost centres<br />

and cost.<br />

and product codes.<br />

A developed marketing Customer data such<br />

strategy including<br />

as new members per<br />

awareness <strong>of</strong> cost per marketing activity,<br />

acquisition, average de-activated and re-<br />

revenue per user, churn, activated members,<br />

and customer lifetime transactions per<br />

value.<br />

member, etc.<br />

V) Integrate systems<br />

ID opportunity Benefit obstacle Change requirement System requirement<br />

1 Create a network <strong>of</strong> branches. No customer can harm the<br />

SACCO by exploiting lack <strong>of</strong><br />

coordination.<br />

A comprehensive and<br />

up-to-date picture <strong>of</strong><br />

the SACCO is available to<br />

management at all times,<br />

reducing risk significantly.<br />

The SACCO reflects and<br />

is more aligned with its<br />

customers who are not<br />

stationary but might<br />

interact with multiple<br />

branches.<br />

Complete customer data is<br />

continuously available.<br />

The available<br />

infrastructure in rural<br />

parts <strong>of</strong> <strong>Kenya</strong> has as<br />

<strong>of</strong> yet proven to be<br />

insufficient to provide<br />

sufficient connectivity<br />

to integrate a multibranch<br />

SACCO on<br />

one instance <strong>of</strong> the<br />

application.<br />

The vendors try<br />

to optimise the<br />

applications to<br />

be ‘light’ in the<br />

sense that the data<br />

transfer requirement<br />

is minimised but<br />

some <strong>SACCOs</strong><br />

still experience<br />

performance issues.<br />

This could <strong>of</strong> course<br />

still be mainly due to<br />

the bandwidth and<br />

not the application.<br />

Not applicable. Satisfactory connectivity<br />

between branches and<br />

head <strong>of</strong>fice.<br />

The system needs to have<br />

the ability to provide the<br />

application remotely either<br />

a client-server structure or<br />

as a web application.<br />

Coordinate multiple<br />

installations through<br />

a robust structure that<br />

prevents remote locations<br />

from falling out <strong>of</strong> sync with<br />

head <strong>of</strong>fice and transact<br />

when the connection is not<br />

available.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!